[BUG] Repeating stream delivery completion drops the installed proxy backend #11

Closed
opened 2026-09-29 04:38:28 +02:00 by erikinkinen · 0 comments
Owner

Summary

The semantic endpoint table permits finish on a live inherited proxy after backend installation. The source column has already changed from the temporary factory capability to the retained lender alias. A repeated completion therefore drops the installed backend and leaves the live receiver without its forwarding authority. Source review found this lifecycle error while implementing recipient-view disposal; no public runtime route triggering the repetition has been demonstrated.

Reproduction

In the semantic fixture, prepare an inherited proxy, install its received backend using finish_inherited, then call finish again on the same original handle. The old source follows the Live branch and calls drop_cap_until_absent on the reused source column. This is a source-derived reproduction sequence, not an executed test result. The authored regression asserts refusal before any native DROP and then uses the surviving proxy.

Expected and actual behavior

Expected: once backend installation is complete, generic factory-source completion returns InvalidState without changing the backend or receiver. Ordinary unfinished factory cleanup may still use its documented retry behavior.

Actual in the reviewed source: the call returns success after deleting the proxy backend because the same ownership bit represents both successive uses of the source column. Subsequent forwarding cannot use that missing alias. This is a lifecycle/availability defect; no authority expansion is claimed.

Environment and identity

  • Component: Launchd revision f9a7d21c30b6619512721769d6191d1de81f812d, branch feature/posix-compat.
  • Integration image graph: unchanged; image adoption is separate ongoing work.
  • Configuration: allocation-free semantic stream endpoint table; no VM or native image reproduction performed.
  • Relevant authority: original authenticated loan and its retained backend SEND plus private receiver; no new capability is granted by the repeated call.
  • Toolchain/hardware: not relevant to the inspected control flow; no compiler or runtime result is claimed.
  • Last known working revision: unknown.

Evidence and prior checks

Implemented in launchd c0737afa: generic completion refuses an installed proxy backend before any DROP. The authored regression preserves the backend and exercises the surviving proxy. Implementation, source audit, test authoring, documentation and signed publication are complete; test execution is waived by user instruction, with no pass claimed.

See the reviewed completion method and backend installation. A state guard and a regression control are being published. Tests, builds, lint checks and CI observation remain deferred by user instruction; no test pass is claimed.

Tracking

## Summary The semantic endpoint table permits `finish` on a live inherited proxy after backend installation. The source column has already changed from the temporary factory capability to the retained lender alias. A repeated completion therefore drops the installed backend and leaves the live receiver without its forwarding authority. Source review found this lifecycle error while implementing recipient-view disposal; no public runtime route triggering the repetition has been demonstrated. ## Reproduction In the semantic fixture, prepare an inherited proxy, install its received backend using `finish_inherited`, then call `finish` again on the same original handle. The old source follows the Live branch and calls `drop_cap_until_absent` on the reused source column. This is a source-derived reproduction sequence, not an executed test result. The authored regression asserts refusal before any native DROP and then uses the surviving proxy. ## Expected and actual behavior Expected: once backend installation is complete, generic factory-source completion returns InvalidState without changing the backend or receiver. Ordinary unfinished factory cleanup may still use its documented retry behavior. Actual in the reviewed source: the call returns success after deleting the proxy backend because the same ownership bit represents both successive uses of the source column. Subsequent forwarding cannot use that missing alias. This is a lifecycle/availability defect; no authority expansion is claimed. ## Environment and identity - Component: Launchd revision `f9a7d21c30b6619512721769d6191d1de81f812d`, branch `feature/posix-compat`. - Integration image graph: unchanged; image adoption is separate ongoing work. - Configuration: allocation-free semantic stream endpoint table; no VM or native image reproduction performed. - Relevant authority: original authenticated loan and its retained backend SEND plus private receiver; no new capability is granted by the repeated call. - Toolchain/hardware: not relevant to the inspected control flow; no compiler or runtime result is claimed. - Last known working revision: unknown. ## Evidence and prior checks Implemented in [launchd `c0737afa`](https://git.erikinkinen.fi/erix/launchd/commit/c0737afa2c91578b4aaa0afbcd0f374dd769562d): generic completion refuses an installed proxy backend before any DROP. The authored regression preserves the backend and exercises the surviving proxy. Implementation, source audit, test authoring, documentation and signed publication are complete; test execution is waived by user instruction, with no pass claimed. See the [reviewed completion method](https://git.erikinkinen.fi/erix/launchd/src/commit/f9a7d21c30b6619512721769d6191d1de81f812d/src/stream_endpoint.rs) and [backend installation](https://git.erikinkinen.fi/erix/launchd/src/commit/f9a7d21c30b6619512721769d6191d1de81f812d/src/stream_proxy_endpoint.rs). A state guard and a regression control are being published. Tests, builds, lint checks and CI observation remain deferred by user instruction; no test pass is claimed. ## Tracking - [Launch ownership and binding](https://git.erikinkinen.fi/erix/launchd/issues/1) - [Launchd implementation review](https://git.erikinkinen.fi/erix/launchd/pulls/2) - [Phase 6 completion](https://git.erikinkinen.fi/erix/integration/issues/65)
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#11
No description provided.