Skip to content

fix(crawl): wait at most 30 s between crawl_busy stop retries - #34

Merged
StefanoGuerrini merged 1 commit into
crawl-stop-retry-busyfrom
crawl-stop-retry-busy-cap
Oct 12, 2026
Merged

StefanoGuerrini merged 1 commit into
crawl-stop-retry-busyfrom
crawl-stop-retry-busy-cap

Conversation

@StefanoGuerrini

@StefanoGuerrini StefanoGuerrini commented Oct 12, 2026 •

Copy link
Copy Markdown
Contributor

Small follow-up for the stop retry on 503 crawl_busy, targeting this PR's branch so it lands with it.

  • stop waited whatever Retry-After the server sent; a value of 3600 made one stop wait an hour. It now waits at most 30 s.
  • A missing or unusable Retry-After (negative, NaN) waits 1 s instead of failing.
  • One test covers the cap.

The base PR (feat/crawl-client-v2) now caps every other Retry-After wait at 30 s too, so the clients agree. Each repo's own checks pass on this branch: lint, typecheck and the full test suite.

Squash-merge with the title as the message: the commit carries trailer lines that should not land.

stop waited whatever Retry-After the server sent, so a value of 3600
made one stop wait an hour. It now waits at most 30 s, and 1 s when the
header is missing or unusable (negative, NaN).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01HJnfsEB5DBXR4e7KxBqvJV
@StefanoGuerrini
StefanoGuerrini merged commit 4710a84 into crawl-stop-retry-busy Oct 12, 2026
1 check passed
@StefanoGuerrini
StefanoGuerrini deleted the crawl-stop-retry-busy-cap branch October 12, 2026 13:49
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.

2 participants