Repository navigation
0.40.3 — slow Seedance 2.5 jobs finish, and the poll budget stays inside its authorization - #112
Merged
Merged
Conversation
…ide its authorization
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Release 0.40.3. Ships the two video polling fixes already on
main(#110, #111) — this PR only bumps the version and writes the changelog, which is what wakespublish.yml.What users get
blockrun_videono longer gives up on slow Seedance 2.5 jobs. Production 30s clips measured 479s, 400s and 275s against a 300s client-side cap, so two of three failed on a limit that had nothing to do with the gateway. Budget is now 540s.The follow-up matters as much: a 540s budget under a 600s payment authorization only looks like it leaves a minute of margin. The deadline check bounds when a poll may start, not when it finishes, so the 5s interval plus the 90s poll timeout pushed the last poll to 635s — 35s past
validBefore. Settlement happens server-side on the completed poll, so that tail would fail settlement for a video that actually rendered. The loop now clamps its last poll to the remaining budget, pinning worst-case wall time at exactly 540s.Scope
Version + changelog only. No source changes —
src/landed in #110 and #111.Deliberately excluded: the in-progress
keychain/walletwork in the local tree. That's unrelated to this fix and unreviewed, so it isn't riding along.Validation
npm run build,npm run typecheck,npm test(343 passed) all clean on this branch — the same gatepublish.ymlruns before publishing.After merge
publish.ymlfires on thepackage.jsonchange and handles all four targets: npm publish, MCP registry (mcp-publisher),v0.40.3tag, and the GitHub release. Each is independently version-gated, so a partial re-run is safe.