Recover WebRTC file transfers through GMCP signalling - #93
Merged
Conversation
github-actions Bot
pushed a commit
that referenced
this pull request
Jul 30, 2026
Recover WebRTC file transfers through GMCP signalling 272827c
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.
Summary
Root cause
Recovery rebuilt the peer connection inside
WebRTCServicebut never handed control back toFileTransferManager, the owner of the offer/answer signalling path. Multiple recovery calls also had no shared in-flight guard.Verification
npm test -- src/WebRTCService.test.ts src/FileTransferManager.test.ts(82 passed)npm test(1,042 passed)npm run typecheckCloses #72