fix: agent mode 'No response received' — pool recycling mid-request#32
Merged
Conversation
For mobile debugging where console isn't available. Clears all chat_ prefixed localStorage keys then reloads cleanly.
The connection pool could recycle a WebSocket client while a chat request was still waiting for response events. This caused 'No response received' because the new client didn't have the event handler. Added hold/release mechanism so active requests pin their client until the stream completes.
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
1 participant
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.
The gateway connection pool was recycling WebSocket clients every 5 minutes, even during active chat requests. If the pool recycled between sending a message and receiving the response, the event handler was on the old (now closed) client. Added a hold/release mechanism to pin clients during active requests.