server: own standalone WebRTC sweep - #926
Merged
yisding merged 1 commit intoAug 7, 2026
Merged
Conversation
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
yisding
marked this pull request as ready for review
August 7, 2026 02:44
yisding
force-pushed
the
agent/ws25-standalone-webrtc-sweep-scope
branch
from
August 7, 2026 03:07
bd19437 to
05c0b8a
Compare
yisding
force-pushed
the
agent/ws25-standalone-webrtc-sweep-scope
branch
from
August 7, 2026 03:48
05c0b8a to
ac49f26
Compare
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
Standalone WebRTC shutdown created its final forced
SessionManager.stop_all()sweep with rawasyncio.create_task(). A hard timeout can intentionally return while cancellation-resistant Session teardown is still unwinding, so this is exactly the kind of survivor that requires explicit ownership.Changes
RuntimeTaskScopeeasycat-standalone-webrtc-session-sweepWhy / impact
A timed-out final sweep remains strongly owned while it reacts to cancellation instead of becoming an anonymous background task. Completed failure reports continue to retain Session ledgers and surface the same shutdown error.
Root cause
The standalone server's final sweep used the hard-timeout helper's legacy background retention but had not been migrated to the named task ownership model in WS2.5.
Checks
webrtc_routes.py— passed