Skip to content

fix(indexer): treat a ready A/B builder as done even if it resumed - #131

Merged
aminsammara merged 1 commit into
mainfrom
amin/box-deploy-ready-check
Nov 5, 2026
Merged

aminsammara merged 1 commit into
mainfrom
amin/box-deploy-ready-check

Conversation

@aminsammara

Copy link
Copy Markdown
Collaborator

Rerunning a deploy with the same new_schema hangs for the full 45-minute timeout. The builder resumes the schema it already built, and Ponder doesn't print 'Completed backfill indexing' on a resume. That's how the second atp-indexer-si-v3 attempt failed.

The wait loop now also checks the builder's /ready on port 42069. The log check is kept.

box-deploy waited for the builder to log 'Completed backfill indexing'. Ponder prints that
line only when it builds a schema from scratch. Rerunning a deploy with the same NEW_SCHEMA
restarts the builder on a schema that is already built, so Ponder resumes, never prints the
line, and the script sits out its full 45-minute timeout before giving up. That is what
happened on the second atp-indexer-si-v3 attempt, with prod already down.

The wait now also accepts the builder's /ready, which Ponder serves once historical indexing
is caught up whichever way it got there. The log check stays as well, in case /ready is slow
to answer on a fresh build.
@aminsammara
aminsammara requested a review from a team as a code owner November 5, 2026 11:35
@aminsammara
aminsammara merged commit a1a38b7 into main Nov 5, 2026
5 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