-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: Enhanced zpa rate-limit with retry-after header tracking #100
Merged
Conversation
This file contains 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
willguibr
had a problem deploying
to
ZPA_PROD_TENANT01
May 28, 2024 22:31
— with
GitHub Actions
Error
willguibr
added
bug
Something isn't working
enhancement
New feature or request
python
Pull requests that update Python code
In development
Under active development
new-acceptance-tests
New acceptance tests
new-attributes
ZPA API Added New Parameters
ZPA New API Resources
ZPA New API Resources
labels
May 28, 2024
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #100 +/- ##
==========================================
+ Coverage 60.50% 66.33% +5.82%
==========================================
Files 53 52 -1
Lines 3773 3915 +142
==========================================
+ Hits 2283 2597 +314
+ Misses 1490 1318 -172 ☔ View full report in Codecov by Sentry. |
willguibr
had a problem deploying
to
ZPA_PROD_TENANT01
May 28, 2024 23:23
— with
GitHub Actions
Error
willguibr
had a problem deploying
to
ZPA_PROD_TENANT01
May 29, 2024 00:37
— with
GitHub Actions
Error
willguibr
temporarily deployed
to
ZPA_PROD_TENANT01
May 29, 2024 06:44
— with
GitHub Actions
Inactive
willguibr
had a problem deploying
to
ZPA_QA_TENANT01
May 29, 2024 06:53
— with
GitHub Actions
Failure
willguibr
temporarily deployed
to
ZPA_PROD_TENANT01
May 29, 2024 08:08
— with
GitHub Actions
Inactive
willguibr
temporarily deployed
to
ZPA_PROD_TENANT01
May 29, 2024 17:12
— with
GitHub Actions
Inactive
github-actions bot
pushed a commit
that referenced
this pull request
May 29, 2024
### [0.3.1](v0.3.0...v0.3.1) (2024-05-29) ### Bug Fixes * Enhanced zpa rate-limit with retry-after header tracking ([#100](#100)) ([afda28e](afda28e))
🎉 This PR is included in version 0.3.1 🎉 The release is available on PyPI and GitHub release
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
bug
Something isn't working
enhancement
New feature or request
In development
Under active development
new-acceptance-tests
New acceptance tests
new-attributes
ZPA API Added New Parameters
python
Pull requests that update Python code
released
ZPA New API Resources
ZPA New API Resources
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.
Provide a general summary of your changes in the title above. You should
remove this overview, any sections and any section descriptions you
don't need below before submitting. There isn't a strict requirement to
use this template if you can structure your description and still cover
these points.
Description
Describe your changes in detail through motivation and context. Why is
this change required? What problem does it solve? If it fixes an open
issue, link to the issue using GitHub's closing issues keywords1.
Has your change been tested?
Explain how the change has been tested and what you ran to confirm your
change affects other parts of the code. Automated tests are generally
expected and changes without tests should explain why they aren't
required.
Screenshots (if appropriate):
Types of changes
What sort of change does your code introduce/modify?
Checklist: