[BUG] Losing one request reply destroys a surviving recipient stream view #12
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#12
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
The inherited-stream runtime cancels an entire dedicated recipient view whenever reply delivery returns native NOT_FOUND, including a lost status/read/write reply. Request abandonment therefore destroys the descriptor's provider while its client and realm remain live.
Reproduction
Source-level reproduction; no VM or test was run. Prepare a dedicated recipient view, issue a status or data operation, then abandon that invocation before its reply is accepted. In
src/runtime/stream_proxy.rs, the NOT_FOUND branch callscancel_recipient_stream_viewand then finishes receiver disposal. A subsequent request through the original still-open descriptor has lost its provider endpoint.Expected and actual behavior
Expected: loss of a status/data reply retires only that request. Keep the originally delegated view available until explicit Close or owning-client/realm teardown. A Close that already disposed backend custody must still finish receiver retirement after its reply is delivered or abandoned. Do not replay committed data or manufacture rollback.
Actual: every lost reply on a recipient view initiates cancellation, drops its backend and receiver, and releases its provider reservation. Ordinary inherited-proxy loss semantics and explicit view Close have separate ownership contracts and must remain intact.
Environment and identity
src/runtime/stream_proxy.rsandsrc/stream_recipient_view.rs.Evidence and prior checks
Implemented in the signed original correction, with three authored, unrun controls and updated component/manual contracts. The runtime now preserves a live recipient view after request loss and completes receiver retirement only when view cancellation already committed. The independent owned-intake defect remains open.
The runtime's NOT_FOUND branch unconditionally cancels recipient views. The existing
finish_recipient_stream_replyalready distinguishes an explicitly cancelled view awaiting its reply from a still-live view. Use that original state at the actual reply boundary, with controls for preserved subsequent I/O, lost Close replies, ordinary proxies and failed/stale evidence. Tests, builds and CI observation remain deferred; no executed result is claimed.Tracking
Related stream consumer, provider review, native scenario and phase completion. This is a request-versus-descriptor lifetime defect; no extra capability or broader access is required to fix it.
erikinkinen referenced this issue from erix/posixd2026-09-29 11:44:53 +02:00
erikinkinen referenced this issue from erix/posixd2026-09-29 11:44:54 +02:00
erikinkinen referenced this issue from erix/integration2026-09-29 11:44:54 +02:00
erikinkinen referenced this issue2026-09-29 11:44:58 +02:00
erikinkinen referenced this issue from erix/posixd2026-09-29 11:44:58 +02:00
erikinkinen referenced this issue from erix/docs2026-09-29 11:45:00 +02:00
erikinkinen referenced this issue from erix/integration2026-09-29 11:45:02 +02:00