Fix OWASP "Secondary Rate Limit" error in CI runs #304
Conversation
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
Upgrade OWASP Scan from v0.10.0 -> v0.11.0 which includes a rate-limit/throttling fix that should get rid of the failures for hitting the "secondary rate limit". See: zaproxy/action-full-scan#93
allthesignals
approved these changes
Oct 2, 2024
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.
Ticket
N/A
Changes
Upgrade OWASP Scan from v0.10.0 -> v0.11.0 which includes a
rate-limit/throttling fix that should get rid of the failures for
hitting the "secondary rate limit".
See: zaproxy/action-full-scan#93
Context for reviewers
N/A
Testing
N/A