fix: use /api/v3 gateway paths in WaveSpeedClient#16
Merged
Conversation
py/wavespeed_api/client.py (imported by the registered wavespeed_predictor
node) still called the legacy /api/v2 gateway for prediction-result polling
and binary media upload. New orgs (id >= 500000) are now blocked from v1/v2 by
the api-server legacy gate, so these calls would 403 for new accounts.
Switch them to /api/v3 (identical {code,message,data} envelope; both routes
exist under v3). The other node paths (wavespeed_api_utils.py,
wavespeed_predictor.py, wavespeed_api_endpoints.py) were already on v3; this
also fixes a stale v2 docstring. Bumps version 2.0.0 -> 2.0.1.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
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
1 participant
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.
Why
py/wavespeed_api/client.py(imported by the registeredwavespeed_predictornode) still called the legacy/api/v2gateway for prediction-result polling and binary media upload. New orgs (id ≥ 500000) are now blocked from v1/v2 by the api-server legacy gate, so these calls would 403 for new accounts.What
client.py:/api/v2/predictions/{id}/resultand/api/v2/media/upload/binary(×2) →/api/v3/.../api/v2docstring inwavespeed_api_endpoints.py2.0.0→2.0.1The v3 routes use the identical
{code,message,data}envelope (client already checkscode != 200) and both exist under v3, so this is path-only. The other node modules were already on v3.Verification
python3 -m py_compileclean on both files.🤖 Generated with Claude Code