Skip to content

fix: a required promoted claim is never sent to a warm peer; the Python SDK asks for the promoted template - #264

Merged
CMGS merged 2 commits into
mainfrom
fix/require-promoted-redirect
Sep 28, 2026
Merged

CMGS merged 2 commits into
mainfrom
fix/require-promoted-redirect

Conversation

@CMGS

@CMGS CMGS commented Sep 28, 2026

Copy link
Copy Markdown
Contributor

Two findings from the docs re-check, each with a regression test that fails on the old code:

  • sandboxd: redirectClaim offered the warm candidates before the template owners, and that redirect carries no require_promoted, so a raw API caller following it could take a pool VM; a required claim now goes only to the template's owners (with require_promoted), else 404. The SDKs and the operator always re-send their own flag, so this closes the raw-caller path and saves the operator a hop.
  • sdk/python: Template.new sends require_promoted, mirroring the Go SDK fix in review: closing round 2026-09-28 #260 (900b2c6).

…irected to a warm peer

redirectClaim offered the warm candidates first, and that redirect carries no require_promoted, so a raw caller following it took a pool VM the docs promise it never gets; a required claim now goes only to the template's owners, else 404.
…irst request

The Go SDK's 900b2c6 fix, mirrored: a stale Python handle could take a warm VM or cold-boot an image named like the template.
@CMGS
CMGS merged commit c19a899 into main Sep 28, 2026
2 checks passed
CMGS added a commit that referenced this pull request Sep 28, 2026
…to a warm peer at quota either (#265)

#264 kept the warm redirect out of the missing-template branch; the quota branch after ClaimProvision still offered the warm candidates without require_promoted. A required claim at quota answers 429.
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