[BUG] Publisher alarm expires at the initial quiet deadline after progress #20

Open
opened 2026-10-14 12:22:14 +02:00 by erikinkinen · 2 comments
Owner

Summary

The pending manual publisher can cancel an operation that is still making progress. Its cancellation alarm keeps the initial quiet deadline even after transferred bytes move the quiet endpoint.

Reproduction

Select a total allowance longer than the quiet allowance, start the cancellation owner, and transfer bytes before each quiet interval expires. Continue beyond the initial quiet endpoint. Cancellation.enter arms the alarm with owner.timeout(owner.deadline); Owner.progress updates last_progress without changing that alarm.

This is a finding in the pending implementation, not a released-image or clean-checkout regression.

Expected and actual behavior

Progress may move the quiet endpoint while the original total deadline stays fixed. Instead, the alarm still expires at the initial quiet endpoint and raises cancelled-or-deadline.

The contained slow-response case exits 1 with that generic category. It demonstrates cancellation, but its status-only oracle does not establish the intended progress-relative quiet behavior.

Environment and identity

Pending Docs publisher under issue 16, based on e66ff449. Linux x86-64, selected Python 3.14 and original Integration command owner 4a87840c0343314fdc1957dc64bcf07c1d4c9a2a. Observations use only designated localhost fixtures; no production credential or request is involved.

Evidence and prior checks

Source inspection establishes the unchanged initial alarm. The actual slow-response receipt retains cancelled-or-deadline, one GET, no later mutation and confirmed original process cleanup. The positive eight-request TLS case and hostname, CA and GET refusals remain useful narrower results; they do not prove this clock behavior.

Tracking

Publisher design, manual review, phase completion.

  • Keep the cancellation timer tied to the original total deadline and each blocking wait tied to its current quiet/operation endpoint.
  • Cover continuous progress beyond the initial quiet interval without renewing the total deadline.
  • Require a specific quiet-expiry result and preserve the exact first error with independent cleanup.
## Summary The pending [manual publisher](https://git.erikinkinen.fi/erix/docs/issues/16) can cancel an operation that is still making progress. Its cancellation alarm keeps the initial quiet deadline even after transferred bytes move the quiet endpoint. ## Reproduction Select a total allowance longer than the quiet allowance, start the cancellation owner, and transfer bytes before each quiet interval expires. Continue beyond the initial quiet endpoint. `Cancellation.enter` arms the alarm with `owner.timeout(owner.deadline)`; `Owner.progress` updates `last_progress` without changing that alarm. This is a finding in the pending implementation, not a released-image or clean-checkout regression. ## Expected and actual behavior Progress may move the quiet endpoint while the original total deadline stays fixed. Instead, the alarm still expires at the initial quiet endpoint and raises `cancelled-or-deadline`. The contained slow-response case exits 1 with that generic category. It demonstrates cancellation, but its status-only oracle does not establish the intended progress-relative quiet behavior. ## Environment and identity Pending Docs publisher under [issue 16](https://git.erikinkinen.fi/erix/docs/issues/16), based on [e66ff449](https://git.erikinkinen.fi/erix/docs/commit/e66ff4497f2d8237c4152f56a28bdbc6297cfb83). Linux x86-64, selected Python 3.14 and original Integration command owner `4a87840c0343314fdc1957dc64bcf07c1d4c9a2a`. Observations use only designated localhost fixtures; no production credential or request is involved. ## Evidence and prior checks Source inspection establishes the unchanged initial alarm. The actual slow-response receipt retains `cancelled-or-deadline`, one GET, no later mutation and confirmed original process cleanup. The positive eight-request TLS case and hostname, CA and GET refusals remain useful narrower results; they do not prove this clock behavior. ## Tracking [Publisher design](https://git.erikinkinen.fi/erix/docs/issues/16), [manual review](https://git.erikinkinen.fi/erix/docs/pulls/4), [phase completion](https://git.erikinkinen.fi/erix/integration/issues/65). - [x] Keep the cancellation timer tied to the original total deadline and each blocking wait tied to its current quiet/operation endpoint. - [x] Cover continuous progress beyond the initial quiet interval without renewing the total deadline. - [x] Require a specific quiet-expiry result and preserve the exact first error with independent cleanup.
Author
Owner

The pending publisher now ties its cancellation alarm to the original total deadline and uses the current quiet endpoint for each blocking wait. The progress and quiet-expiry cases pass, and the original timeout error survives cleanup. The three implementation criteria are checked. This issue stays open until the corrected publisher is adopted under #16; no released-source fix is claimed.

The pending publisher now ties its cancellation alarm to the original total deadline and uses the current quiet endpoint for each blocking wait. The progress and quiet-expiry cases pass, and the original timeout error survives cleanup. The three implementation criteria are checked. This issue stays open until the corrected publisher is adopted under [#16](https://git.erikinkinen.fi/erix/docs/issues/16); no released-source fix is claimed.
Author
Owner

14e36d18 adopts the bounded manual publisher and removes the old shell implementation. The source cohort and publication inputs are explicit, with one total deadline and fail-closed retirement. The original CI completes the strict render but fails at publication; #23 tracks that separate defect.

`14e36d18` adopts the bounded manual publisher and removes the old shell implementation. The source cohort and publication inputs are explicit, with one total deadline and fail-closed retirement. The original CI completes the strict render but fails at publication; [#23](https://git.erikinkinen.fi/erix/docs/issues/23) tracks that separate defect.
erikinkinen added this to the Alpha 1 milestone 2026-10-30 09:33:40 +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/docs#20
No description provided.