Skip to content

Harden price-backfill against transient fetch failures#17

Merged
icemansparks merged 1 commit into
merkerhoodfrom
feat/retry-hardening
Jul 1, 2026
Merged

Harden price-backfill against transient fetch failures#17
icemansparks merged 1 commit into
merkerhoodfrom
feat/retry-hardening

Conversation

@icemansparks

Copy link
Copy Markdown
Collaborator

Problem

A clean full run (no redeploy, build_gen=0) still left ~11% of items as fetch-failed — transient HTTP/network errors that survived the per-request retries under sustained ~90-min load. These items just weren't reached; not corrupt data, but an incomplete run that needed a manual gentle re-fetch to salvage (happened on both the price run and the item-count run).

Fix

  • wowauctions._get retries raised 3 -> 5 (exponential backoff unchanged).
  • New bounded end-of-run re-sweep: after the main pass and redeploy-recovery, re-fetch any fetch-failed items for --resweep-rounds (default 2) passes until none remain. Mirrors the existing redeploy-recovery structure; transient failures clear on a later attempt.

Tests

43 passing, incl. a new select_fetch_failed test. README documents --resweep-rounds and the behavior.

A clean (non-redeploy) full run left ~11% of items as fetch-failed — transient
HTTP/network errors under sustained load, not a data gap. Raise _get retries
3->5 and add a bounded end-of-run re-sweep (--resweep-rounds, default 2) that
re-fetches fetch-failed items until none remain, so a single run no longer needs
a manual gentle salvage.
@icemansparks
icemansparks merged commit 719a969 into merkerhood Jul 1, 2026
1 check 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