Repository navigation
Don't rearm WebSocket heartbeat after close - #14236
rinopatrick wants to merge 2 commits into
Conversation
Automation signalsActivity patterns show signs of automation. Evidence
Last 5 PRs: This is an automated analysis by AgentScan |
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #14236 +/- ##
========================================
Coverage 99.11% 99.11%
========================================
Files 135 135
Lines 53338 53452 +114
Branches 2717 2725 +8
========================================
+ Hits 52865 52978 +113
Misses 359 359
- Partials 114 115 +1
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Harness. |
[Low impact] The PR appears safe to merge; no outstanding findings remain. Reviews (2) · Last reviewed commit: "fix(changelog): add PR-numbered symlink" · Reviewed by Greptile |
Merging this PR will not alter performance1 warning
Comparing Footnotes
|
Closes #14125.
Peer-close data arriving after the close handshake scheduled a deferred heartbeat reset (via call_soon); when it ran, _reset_heartbeat re-created the heartbeat timer on a connection whose public closed property was already true. The deferred reset is now dropped when the connection is closing or closed.
Tests: new test_flush_heartbeat_reset_does_not_rearm_after_close (fails before, passes after); full test_web_websocket.py green (63 passed).