[BUG] Deferred stream Close can redispatch its result and remain pending indefinitely #18

Open
opened 2026-10-12 13:00:43 +02:00 by erikinkinen · 0 comments
Owner

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

  • Component repository/revision and Integration source graph: original launchd source, original Integration graph.
  • Image profile, digest and build/runtime configuration: maintained host validation and selected component workflow; no guest image is claimed by this report.
  • Hardware or VM, architecture, firmware and toolchain versions: x86_64 host with the workflow-selected toolchain; no hardware or firmware-specific cause is inferred.
  • Input/session route and granted authority relevant to reproduction: explicit source graph and local validation inputs; no additional runtime authority is introduced.
  • Last known working revision, if known: not established.

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.

## 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 - Component repository/revision and Integration source graph: [original launchd source](https://git.erikinkinen.fi/erix/launchd/commit/26dc2bed056e892890f97cb92ce06c6f02cdc2ba), [original Integration graph](https://git.erikinkinen.fi/erix/integration/commit/a615de2f69c25d4575d0c349757a0017082f988b). - Image profile, digest and build/runtime configuration: maintained host validation and selected component workflow; no guest image is claimed by this report. - Hardware or VM, architecture, firmware and toolchain versions: x86_64 host with the workflow-selected toolchain; no hardware or firmware-specific cause is inferred. - Input/session route and granted authority relevant to reproduction: explicit source graph and local validation inputs; no additional runtime authority is introduced. - Last known working revision, if known: not established. ## 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](https://git.erikinkinen.fi/erix/integration/issues/65) tracks the full remaining goal. Signed source fixes, coherent dependency adoption and exact validation results will be recorded before closure.
erikinkinen added this to the Alpha 1 milestone 2026-10-30 09:34:32 +01:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
erix/launchd#18
No description provided.