You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Open Processing API will be updating to allow consumers to pass a BEARER token into their request which will allow them to bypass rate limits.
When this is ready, p5.js website can be updated to use this token when compiling static-builds.
Required changes:
For GHA/deployment, this token can be added to the action secrets for this repo, and the build workflow files should be updated to use this token when making calls to OP API.
For local builds by open-source contributors, if the token is not shared, there may need to be updates to contribution documentation to indicate that local builds may fail due to hitting rate limits, but will not do so when automated tests run on open PRs.
Would you like to work on this issue?
Happy to do so, or have it be assigned -- I think the part where the token is added to GHA secrets will require admin access to the repo, but I'm happy to do the GHA workflow file updates once the token is added
The text was updated successfully, but these errors were encountered:
Uh oh!
There was an error while loading. Please reload this page.
Follow-up for: #831 (comment)
Context:
Open Processing API will be updating to allow consumers to pass a BEARER token into their request which will allow them to bypass rate limits.
When this is ready, p5.js website can be updated to use this token when compiling static-builds.
Required changes:
For GHA/deployment, this token can be added to the action secrets for this repo, and the
build
workflow files should be updated to use this token when making calls to OP API.For local builds by open-source contributors, if the token is not shared, there may need to be updates to contribution documentation to indicate that local builds may fail due to hitting rate limits, but will not do so when automated tests run on open PRs.
Would you like to work on this issue?
Happy to do so, or have it be assigned -- I think the part where the token is added to GHA secrets will require admin access to the repo, but I'm happy to do the GHA workflow file updates once the token is added
The text was updated successfully, but these errors were encountered: