Skip to content

Retain bounded diagnostics for intermittent network summary failures #569

Closed

Description

@pithead-developer

Worker brief

Related unresolved failure: #563. The operator authorized this diagnostics prerequisite on maintenance & gates, reusing existing draft PR #568. No second implementation or PR is needed.

The nightly summary metadata/key assertion failed once; the retained failure lacks enough observations to identify a cause. Both the isolated network phase and the nightly prefix subsequently passed without a product fix. This prerequisite supplies bounded instrumentation for a future recurrence; it does not resolve #563.

Acceptance criteria:

  • Emit fixed boolean summary diagnostics without response bodies, key names, timestamps, secrets or parser errors.
  • Preserve the strict summary assertion and failure row in tests/e2e-pithead.sh, plus the existing lock, snapshot and restoration lifecycle.
  • Provide a narrow network-sequence phase reproducing connect → worker-api → api-impact → network in one process/snapshot, stopping on fatal errors or failed rows and omitting later phases.
  • Require regressions for diagnostic sanitization, phase wiring, sequence order/shared state and failure propagation, with corrected test documentation.
  • Require green GitHub checks and current-head rigforge tier4-e2e proof. Completed job 2054@48b227098a8eae72503de741de18d12d740fe6b3 supplies that instrumentation proof; obtain fresh evidence if the head changes.
  • Submit the prerequisite to the separate adversarial-review gate. Author-side verifier/security reviews do not replace that gate.

Implementation and focused tests are complete in PR #568 at 48b227098a8eae72503de741de18d12d740fe6b3; all eight GitHub checks passed. Full logs/status/artifacts of the completed reproductions were audited and their generated evidence is in the PR body.

Only this prerequisite may close when the diagnostic PR lands. #563 stays open on v2 - appliance; after landing, its next evidence source is the scheduled rigforge nightly. Diagnose any recurrence from the full artifacts. Do not run a speculative rerun loop or describe the passing reproductions as a root-cause fix.

Activity

  1. pithead-developer commented on Oct 3, 2026

    @pithead-developer
    ContributorAuthor

    Implementation is complete in existing draft PR #568, which now targets this diagnostics prerequisite. The operator-authorized split and limits are recorded under “Decisions taken.” Current head is 48b227098a8eae72503de741de18d12d740fe6b3; all eight GitHub checks and completed tier4-e2e job 2054@48b227098a8eae72503de741de18d12d740fe6b3 passed. The head has not changed.

    The PR has a Ready for review submission requesting the separate reviewer session and required adversarial-review status. Author-side verifier/security reviews are clean but are not that gate. Please process this prerequisite through review and runner-managed landing; #563 remains the unresolved failure, to resume from scheduled-nightly recurrence evidence after this issue is complete.

  2. pithead-developer commented on Oct 3, 2026

    @pithead-developer
    ContributorAuthor

    Moved into v2 - appliance because #563 depends on this issue in the release dependency chain.

  3. pithead-developer commented on Oct 3, 2026

    @pithead-developer
    ContributorAuthor

    Merged in #568.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions