Repository navigation
refactor(daemon): Part of #3736: T2-S5 background owners on native #3981
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
Merged
ScriptedAlchemy
merged 7 commits into
master
from
refactor/3736-t2-s5-background-owners
Oct 15, 2026
Merged
Changes from all commits
Commits
Show all changes
7 commits
Select commit
Hold shift + click to select a range
c44aeff
refactor(daemon): run background owners on the native runtime
ScriptedAlchemy b06308c
Merge remote-tracking branch 'origin/master' into refactor/3736-t2-s5…
ScriptedAlchemy 66d4273
test(daemon): prove background owners run without Tokio
ScriptedAlchemy f9f5212
test(daemon): prove the PR autotrack owner aborts on drop
ScriptedAlchemy 9d9dcb5
Merge remote-tracking branch 'origin/master' into refactor/3736-t2-s5…
ScriptedAlchemy f7ad6ee
test(daemon): wait on the cancelled loop's end, not a poll
ScriptedAlchemy 066a946
Merge remote-tracking branch 'origin/master' into refactor/3736-t2-s5…
ScriptedAlchemy 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.
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.
🔴 Rejected reaper strands project automation
When
NativeTask::spawnrefuses a reaper, the retired scheduler remains registered asRetiringwithout a task. Later retirement attempts cannot clear it, so project automation cannot restart.Learn more
Retirement first moves the scheduler task out of its registry entry and marks that entry
Retiringin retire_matching_automation_scheduler. Normally, the reaper joins the task and runs the cleanup future, which removes that entry. If native spawn refuses, the finalizer signals termination but never runs cleanup. The entry retainsRetiringwithtask: None; later retirement attempts cannot create another reaper, and scheduler reconciliation returnsRetiring.Example: A project's automation loop starts retiring as the native runtime stops accepting tasks. Reaper spawn fails; the retirement waiter completes, but the project's next automation reconcile still reports
Retiringindefinitely.Recommended fix: Make spawn refusal run or schedule the cleanup after the retired task has actually settled, retaining ownership until then. Avoid publishing termination as completed before the scheduler tombstone is removed; validate a retry can start automation after a refused reaper spawn.
Was this helpful? React with 👍 or 👎 to provide feedback.