Handle revision fetch failures in streamAskQuestion#4204
Open
Handle revision fetch failures in streamAskQuestion#4204
Conversation
|
Contributor
|
The latest updates on your projects. Learn more about Argos notifications ↗︎
|
utkuufuk
approved these changes
Apr 21, 2026
Member
|
Nitpick: how about a warning log for easier debugging? |
SamyPesse
requested changes
Apr 21, 2026
Member
SamyPesse
left a comment
SamyPesse
left a comment
There was a problem hiding this comment.
It should not be handled; it should be fixed in gbx
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Ensure that failures in fetching revisions do not disrupt the entire answer process.
If an error is emitted, we display an error message at the end of the message instead of replacing the entire already displayed response with an error message.