fix: log 503 client error to stderr #3896
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The point of "fix or feat" is to easily decide which version to bump and/or whether to backpatch...
... where Since there is nothing really broken, I wouldn't bother with backpatching. For me, this is an "improvement of an existing feature", not a fix. So |
taimoorzaeem
force-pushed
the
issue3841/log-503
branch
from
597d7d0 to
2079a50
Compare
The |
taimoorzaeem
force-pushed
the
issue3841/log-503
branch
from
2079a50 to
9883843
Compare
taimoorzaeem
changed the title
taimoorzaeem
commented
Feb 5, 2025
taimoorzaeem
force-pushed
the
issue3841/log-503
branch
from
9883843 to
73bddfa
Compare
steve-chavez
approved these changes
Feb 9, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Closes #3841.
Should this go under feat? Maybe we should introduce new commit prefix for logging like maybe
log: ...?