-
Notifications
You must be signed in to change notification settings - Fork 4
Harden relay mode, joins and sub-account publishing #42
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
Open
HashimTheArab
wants to merge
11
commits into
main
Choose a base branch
from
fix/relay-hardening
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
11 commits
Select commit
Hold shift + click to select a range
3139a9f
fix: harden relay mode, joins and sub-account publishing
HashimTheArab e50dca2
fix: keep full sessions that live relayed players mostly hold
HashimTheArab f22a56a
chore: pin gophertunnel to the listener limits PR head
HashimTheArab ca740a3
fix: bound only authentication of joiners and pick up go-xsapi main
HashimTheArab 5e6bf93
fix: refresh relay sessions in parallel and update the primary first
HashimTheArab 0cd658f
fix: space session re-reads for anonymous relay clients
HashimTheArab b8e1e5f
fix: let a relay leg finish forwarding before teardown
HashimTheArab 528f673
refactor: drop the pending login cap default
HashimTheArab c0df99f
fix: relay only clients that prove their login key
HashimTheArab 7a9ad23
docs: correct why Close drains client handlers without the lock
HashimTheArab 122cbaf
fix: give each unpublished sub-account retry its own budget
HashimTheArab 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.
Uh oh!
There was an error while loading. Please reload this page.
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.
🩺 Stability & Availability | 🟠 Major | 🏗️ Heavy lift
Do not hold
b.muacross sub-account publish network calls.retryUnpublishedSubAccountsholdsb.muwhile it callsb.statusandstartSubAccountBounded. Each publish can take up to 90 seconds: XBL client setup, mutual follow, settle delay, and announce. This has two effects:publishedSessionsinrelay.golocksb.mu. While a retry runs, relay joins with unproven login keys block inverifyRelayIdentityfor the full duration.Closerunsb.mu.Lock()beforeb.cancel(). The cancel that would stop the retry happens only afterClosegets the lock, soClosewaits for the full retry.startSubAccountexpectsb.muto be held while it updatessubAnnouncers,subAnnouncersByID, andsubAccountRetries. Split the work into three steps:statusand for creating and announcing the announcer.scheduleSubAccountRetry. Checkb.startedagain at that point.Another option is a narrower lock for the sub-account bookkeeping.
🤖 Prompt for AI Agents
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.
Valid, and partly addressed in 0cd658f. The retry pass now has the same 15s budget as targeted sub-account recovery, instead of 30s. The per-account 90s start timeout is capped by that pass budget, so it never applies here. Holding
b.muacross publish calls is how every session path works today (Update, targeted recovery,recreateSession), andstatusandstartSubAccountdepend on it (lastQuery,createdXBLClients, the account's client and XUID). Splitting that lock is a broader change than this PR and overlaps other in-flight session work, so I'm leaving this thread open for that follow-up.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.
@HashimTheArab, thanks for the clarification. With the 15-second retry-pass budget you describe, my 90-second estimate does not apply to this path. Holdingb.mucan still delay relay identity checks andClose, so I agree with leaving this thread open for the broader locking change.Would you like me to open a follow-up issue for that change?
✏️ Learnings added
You are interacting with an AI system.