Conversation
…iodic prepare path (issue #324)
fix(memory): extend background-maintenance lock discipline to the periodic prepare path (issue #324)
… scan disposal interrupts (review R3)
…, neutral pause msg, interrupt suppression, stronger no-op test)
…kpoint gating at replan/extend (DAG-01/DAG-02)
…l; sync ADR-0003 (review R1)
…ngated hint (review R4)
fix(dag): resolve audit defects DAG-01..04 (fixed-point loop converged)
fix(goal): resolve audit defects GOAL-01..04 (fixed-point loop converged)
…light deferreds (MEM-01/MEM-02 acceptance)
…s before release (review R1)
…oped in-flight key (review R2)
…ion wording (review R4)
fix(memory): matcher calls outside the identity fence, exit-safe in-flight coalescing (acceptance leftovers)
fix(dag): adversarial verification clause on reporting checkpoints (issue #323)
…ance teardown (production incident 2026-08-18)
…nce-aware freeze window (review R1)
…-host comment (review R5)
fix(dag): host-level supervision sweep settles nodes orphaned by instance teardown
Uh oh!
There was an error while loading. Please reload this page.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Incident (2026-08-18, dag_fe5feabfcae607fqVdRh47lN1B)
A per-directory instance teardown mid-run silently reaped every fiber in its scope — DagLoop subscriptions, the spawn fiber, AND the deadline watcher — while the durable node row stayed
running. In a live host nothing re-arms supervision, sosg4-integraterotted inrunningfor 7.5h+ past its deadline withescalation_pending=0,timeout_extensions=0. Recovery can settle such rows, but only re-init/crash triggers it.Fix (via #338, merged to dev; dev CI green)
New host-level service
DagSupervisionSweep(src/dag/runtime/supervision-sweep.ts), wired into AppLayer:timeout_extensionswith a per-node windowfrozenTicksNeeded(escalateIntervalMs) = ceil(max(interval,1s)/60s)+1, cadence read defensively from the persisted workflow config (degrade → DEFAULT 10-min window). A live watcher at ANY configured timeout always moves the counter inside the window.nodeFailed(..., "timeout")under the durable terminal-status guard (cross-host double settles collapse to one). All recovery sites propagate interrupts; failed settles retry next tick.Tests
test/dag/dag-node-supervision.test.ts: healthy control, stream-hang (incident shape), dispose-instance (mechanism + sweep fallback), cancel-defect (production InstanceRef die never blocks the settle; mutation-verified), freeze window (live watcher never swept at production cadence relationship), pure unit tests for cadence derivation/degrade and window boundaries. 9/9 pass locally and in dev CI.Reviewed through a 6-round fixed-point loop (R1–R6); R5/R6 consecutive PASS with zero findings.