[BUG] Retained-output checks do not advance the current producer progress #611

Open
opened 2026-11-08 16:29:50 +01:00 by erikinkinen · 0 comments
Owner

Summary

A new native producer can exhaust its quiet budget while the graph repeatedly checks retained outputs from completed producers. Those checks do real filesystem work, but their passive scopes do not report progress to the current producer.

Reproduction

  1. Run the complete retained native graph with the maintained Directory image scenario and explicit source/tool/signing selections.
  2. Allow completed producer namespaces to accumulate, then admit a subsequent library producer.
  3. Observe the initial graph-retained checkpoint before that producer starts Cargo.

The complete run on the revision below failed at LibIPC admission after 24 prior output products. A smaller three-producer prefix passed and does not reproduce this scale.

Expected and actual behavior

Expected: completed, fully checked retained-output inspections count as actual work for the current producer while all existing checks and original total/quiet limits remain in force.

Actual: MetadataAlarmExpired arose in prepare_source -> graph.check_retained -> other._checkpoint_local -> os.listdir. The current producer had existed for about 36.8 seconds, below its 120-second total limit, and the 7,200-second graph limit remained available. No Cargo invocation had started for that producer. The exact last-progress timestamp was not recorded; the defining budget selection and missing current-producer attribution identify the quiet-accounting path.

Environment and identity

  • Integration revision: 8eddf7f3e7, planning metadata prerequisite.
  • Profile: complete clean Directory image graph, 80 actions, explicit source-history depth one.
  • Platform: Linux x86-64 native build with the original retained tool/source selection.
  • Original limits: graph 7,200 seconds; affected producer 120-second total, 30-second quiet and 15-second retirement.
  • Last complete working whole-graph revision: not established.

Evidence and prior checks

The failed operation ended after 1,786.98 seconds. Original process and source-forest cleanup succeeded without quarantine; no image or VM result exists. Fresh read-only FD-based census measurements found 66,143 namespace entries across 25 roots, traversed in about 3.3 seconds. No single census exceeded 30 seconds. Producer activation performs several complete graph censuses before source preparation, and those repeated inspections currently leave the live producer's quiet receiver unchanged.

Keep every source and namespace guard. Report only actual completed inspections through the same original current producer's progress sink; preserve first failures, short-write handling, counters and deadlines. Do not use timing heartbeats or widen limits.

Tracking

Related prerequisites: catalog compilation-input lifetime, explicit source history and planning metadata. Required regression controls cover genuine completed census delivery, mutation refusal, expired-current refusal, short writes and unchanged original end times.

## Summary A new native producer can exhaust its quiet budget while the graph repeatedly checks retained outputs from completed producers. Those checks do real filesystem work, but their passive scopes do not report progress to the current producer. ## Reproduction 1. Run the complete retained native graph with the maintained Directory image scenario and explicit source/tool/signing selections. 2. Allow completed producer namespaces to accumulate, then admit a subsequent library producer. 3. Observe the initial graph-retained checkpoint before that producer starts Cargo. The complete run on the revision below failed at LibIPC admission after 24 prior output products. A smaller three-producer prefix passed and does not reproduce this scale. ## Expected and actual behavior Expected: completed, fully checked retained-output inspections count as actual work for the current producer while all existing checks and original total/quiet limits remain in force. Actual: MetadataAlarmExpired arose in prepare_source -> graph.check_retained -> other._checkpoint_local -> os.listdir. The current producer had existed for about 36.8 seconds, below its 120-second total limit, and the 7,200-second graph limit remained available. No Cargo invocation had started for that producer. The exact last-progress timestamp was not recorded; the defining budget selection and missing current-producer attribution identify the quiet-accounting path. ## Environment and identity - Integration revision: 8eddf7f3e7b138e4f53d905d1f4e3d0c7c7fa887, [planning metadata prerequisite](https://git.erikinkinen.fi/erix/integration/pulls/609). - Profile: complete clean Directory image graph, 80 actions, explicit source-history depth one. - Platform: Linux x86-64 native build with the original retained tool/source selection. - Original limits: graph 7,200 seconds; affected producer 120-second total, 30-second quiet and 15-second retirement. - Last complete working whole-graph revision: not established. ## Evidence and prior checks The failed operation ended after 1,786.98 seconds. Original process and source-forest cleanup succeeded without quarantine; no image or VM result exists. Fresh read-only FD-based census measurements found 66,143 namespace entries across 25 roots, traversed in about 3.3 seconds. No single census exceeded 30 seconds. Producer activation performs several complete graph censuses before source preparation, and those repeated inspections currently leave the live producer's quiet receiver unchanged. Keep every source and namespace guard. Report only actual completed inspections through the same original current producer's progress sink; preserve first failures, short-write handling, counters and deadlines. Do not use timing heartbeats or widen limits. ## Tracking Related prerequisites: [catalog compilation-input lifetime](https://git.erikinkinen.fi/erix/integration/pulls/603), [explicit source history](https://git.erikinkinen.fi/erix/integration/pulls/606) and [planning metadata](https://git.erikinkinen.fi/erix/integration/pulls/609). Required regression controls cover genuine completed census delivery, mutation refusal, expired-current refusal, short writes and unchanged original end times.
erikinkinen added this to the Alpha 1 milestone 2026-11-08 16:29:50 +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/integration#611
No description provided.