Skip to content

fix(backfill): a malformed provider reply fails one window, not the extract run (T-1722) - #299

Merged
wolverin0 merged 1 commit into
mainfrom
lane/bfresil
Oct 23, 2026
Merged

wolverin0 merged 1 commit into
mainfrom
lane/bfresil

Conversation

@wolverin0

Copy link
Copy Markdown
Owner

Summary

The live AO-7 extract run (campaign ao7-20261022, cohort claude-0) aborted with exit 2 on one Gemini reply that was not a JSON object; the 15-minute scheduled relaunch then re-hit the same window on every start. BackfillRunner._extract now catches ProviderCallError (which includes ProviderOutputError) around the per-window extraction, records last_error on the window and continues. Attempts already count toward the existing three-strike unresolved_extraction and the repair allowance; nothing else changes.

Verification

  • Red first: without the fix the new test propagates ProviderOutputError; with it tests/test_dreaming_backfill_cli.py and tests/test_dreaming_backfill_windowing.py pass (42).
  • ruff, scripts/generate_release_truth.py --check, scripts/check_contract_witness.py green.

🤖 Generated with Claude Code

…t the extract run

One Gemini reply that was not a JSON object raised ProviderOutputError out of
BackfillRunner._extract, exited the run with code 2 and left the scheduled
relaunch re-hitting the same window every 15 minutes. The per-window call now
records the error on the window and continues; the existing three-strike
unresolved_extraction and repair allowance are unchanged. Red-first test with a
fixture extractor failing once.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
@wolverin0
wolverin0 merged commit cb8d2a0 into main Oct 23, 2026
12 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant