Repository navigation
fix: reject native entry after remote lease expiry - #377
Merged
Merged
Conversation
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 native callback waiting for a physical thread could enter host code after its remote lease expired if the runtime and timer driver were stalled. Ready work could also advance before the delayed lease timer ran.
Publish read-only monotonic lease authority, revoke it before supervised futures are destroyed, and check it at physical mobile callback entry and result publication. Keep the existing local handler registration API and StepContext shape compatible.
Validation:
Full CI and Mobile SDK workflow success are required before merge.