Repository navigation
fix(core): retire allocation recovery on native session end - #1399
Merged
Merged
Conversation
Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
|
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
|
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.
A completed native session no longer leaves its durable allocation-recovery record behind and blocks every later launch with
session_allocation_unresolvedwhen discovery is unavailable.The existing account/provider/seat and pending-handoff checks still gate acknowledgement. Exact-seat completion clears durable recovery state before releasing active ownership, preserves ownership if deletion fails, and permits a safe retry. It does not issue a network DELETE for a session that has already authoritatively ended or weaken general recovery cleanup.
Refs #1395. The protocol reference now documents this ordering.
Verification:
Live authenticated Windows gameplay and the exact reported spinner presentation were not exercised.