Repository navigation
fix(dreaming): configurable consolidation timeout and run-scoped fallback after the first hang (T-1793) - #306
Merged
Merged
Conversation
# Conflicts: # ROADMAP.md # docs/generated/release-truth.json # docs/generated/release-truth.md
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 free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
T-1793 (AO-2): the antigravity consolidation stage tripped
consolidate_breaker = TimeoutExpired13 times in the last 14 days.Measurement (read-only, live capture-control database, 2026-10-25, new
scripts/measure_consolidate_latency.py): 238 antigravity consolidation calls since 2026-10-11, 214 ok / 24 error, p50 10.2 s, p95 26.3 s, 24 calls with unknown duration (the hung ones), 13 runs with the TimeoutExpired breaker. So the failures are hangs, not slow calls: a bigger budget alone would not fix them.Change:
MEMORYMASTER_DREAM_CONSOLIDATE_TIMEOUT_SECONDS(60..1800, default 300; existingMEMORYMASTER_AGY_TIMEOUTstill honoured) and, after the first subprocess timeout in a run, the remaining consolidation calls of that run go to the configured extraction provider (recorded asconsolidate_fallback); the timed-out batch waits for a later run. Without a consolidation-capable extractor the existing breaker applies. Model selections are untouched.Evidence (lane-run outside the worker sandbox): tests/test_dreaming_worker.py + tests/test_dreaming_providers.py + tests/test_public_demo.py = 144 passed. Worker: ruff, release-truth --check, contract-witness passed. Follow-up row: 7 days with zero TimeoutExpired breaker runs after install.
🤖 Generated with Claude Code