Repository navigation
fix: retain native task ownership across engine teardown - #378
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 can outlive its logical invocation and its MobileEngine. Admission and quarantine previously belonged to one engine, so a second engine/database could enter a newer claim for the same remote task while the predecessor was still physically running.
Reserve native task ownership process-wide by canonical backend API URL and task UUID before recording started dispatch. Keep that reservation in an enriched lease observer through physical callback and foreign destructor completion. Lease revocation still removes logical authority immediately; retaining physical ownership never renews or activates it. Contended claims are released unstarted, while unrelated tasks and different backends remain independent.
The change is additive to LeaseAuthority and preserves existing handler/SDK interfaces. It does not enable scoped remote execution or a new negotiated capability.
Validation: