Log errors when fibers exit with an error in ResponseLogger
#7678
+5
−2
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.
Today, I was investigating the classic thing when updating dependencies in a service that hasn’t been touched in years, and I was a bit amazed when I found this debug log (kinda cool that it got printed on that running environment though):
... with no additional info, like stack traces or anything meaningful else.
So, I propose to log errors by default for cases fibers exit with an error in
ResponseLogger.