fix(web): recover from quiet or stalled connections - #370
Open
testikun wants to merge 2 commits into
Open
Conversation
14 tasks
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.
Problem
The OpenPI Web event stream could remain silently half-open, and quiet streams gave the browser no bounded way to verify canonical state. API and prompt-admission waits were also unbounded, leaving users without actionable feedback when a connection stalled. This completes the remaining liveness/recovery slice of #363 and is intentionally separate from the state-regression work in #364.
Value
Web clients now detect silent failures, periodically reconcile quiet connections with the canonical snapshot, and retain prompt drafts with explicit localized feedback when admission times out.
Approach
AbortController; preserve failed prompt drafts and surface distinct pending, timeout, error, and reconnecting feedback.Validation
bun run check— passed.bun run test— passed: Node 1244 passed / 1 platform skip; Vitest 30 passed.Impact