Repository navigation
Recover original chat result after unreadable gateway errors - #621
Merged
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
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.
An interrupted Cloudflare connection returned a non-JSON server error while Von continued the original turn. The chat UI incorrectly displayed a terminal failure, although reloading later recovered the completed response.
Unreadable HTTP 5xx responses now use the existing actor-scoped task-result observer, just like a lost response connection. The browser submits the prompt once and displays the original task's eventual success or failure once. JSON application errors and non-server denials retain their current handling.
Validation: 48 tests pass across
chatTabAbortandchatTaskQueue, including simulated 502/503/504/524 responses, canonical task failure after a 502, and non-recovery controls. Static frontend lint and diff checks pass. This repairs response recovery; it does not establish or fix the underlying QUIC network timeout. Tracked in JVNAUTOSCI-2740.