forked from phil65/agentpool
-
Notifications
You must be signed in to change notification settings - Fork 9
feat: Add WebSocket heartbeat configuration support with enhanced logging #51
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
4b9cac1
fix(acp): increase default read timeout for MCP transport and session…
A-Qiang 3991f2a
fix(acp): increase timeout for mcp/connect and mcp/message to 300 sec…
A-Qiang 591e710
feat: Add WebSocket heartbeat configuration support
A-Qiang 8e00feb
feat: Enhance WebSocket heartbeat logging with detailed info and debu…
A-Qiang 8d22ff5
fix: address review feedback — wrap finally cleanup in try-except, re…
Leoyzen File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The current sequential implementation of
_websocket_heartbeatintroduces a drift in the ping interval. Becauseawait asyncio.wait_for(pong_waiter, timeout=pong_timeout)is awaited sequentially afterawait asyncio.sleep(ping_interval), the actual time between pings becomesping_interval + latency(orping_interval + pong_timeouton timeout). This causes the heartbeat to drift and behave inconsistently compared to standard heartbeats (like Uvicorn's, which sends pings at fixed intervals). This also creates a discrepancy betweenWebSocketTransport(which takes 270s to close on 3 missed pongs) andACPWebSocketTransport(which takes 210s to close). Consider scheduling the ping/pong checks concurrently or adjusting the sleep interval to maintain a consistent ping interval.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is intentional. The custom heartbeat is designed to be "forgiving" — it waits for the pong response before sending the next ping, only closing after consecutive missed pongs. This differs from the standard websockets library's fixed-interval approach. The drift is a byproduct of this design choice, not a bug. If precise interval timing becomes necessary in the future, we can switch to absolute-time scheduling.