[BUG] Deferred stream Close can redispatch its result and remain pending indefinitely #18
Labels
No labels
alpha-1
bug
ci
docs
duplicate
enhancement
help wanted
invalid
performance
phase-6
question
refactor
security
wontfix
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
erix/launchd#18
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
Deferred stream Close can redispatch its result and remain pending indefinitely. Maintained validation cannot reach its intended successful boundary.
Reproduction
Run the original stream disposal control that cancels readiness before completing an owned Close. Advance the original invocation after readiness cancellation settles. The original failing source and current repairs are distinct; failures and true exit statuses are retained.
Expected and actual behavior
The maintained source should compile, discover its original controls and complete the specified checks without warnings. dispose_pending remains set when the deferred original Close stores its reply. Later turns treat those result bytes as another request and remain Pending instead of completing the original owner once.
Environment and identity
Evidence and prior checks
Clear the deferred-disposal flag before the once-only original Close dispatch. Preserve its original native invocation and backend/lender lifetime. The strengthened existing regression requires exactly one completion for original owner 2, a successful Reply envelope, one backend alias drop, one receiver drop and the surviving lender. Fresh full validation follows the repaired source.
Tests and exact-head CI now run in parallel with implementation. A skipped, pending or unrun check is not a pass; independent source work continues while regressions are repaired.
Tracking
Phase completion tracks the full remaining goal. Signed source fixes, coherent dependency adoption and exact validation results will be recorded before closure.