ARC-1231 fix preemptive rate limit negative number problem #1934
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
bgvozdev
reviewed
Mar 1, 2023
| log.info({ | ||
| timeToResetInSeconds, | ||
| finalTimeToRestInSeconds, | ||
| coreReset: rateLimitResponse?.resources?.core?.reset, |
There was a problem hiding this comment.
Why just don't log the whole object?
There was a problem hiding this comment.
I feel this should be enough. But I don't have a strong reason either way though.
bgvozdev
approved these changes
Mar 1, 2023
gxueatlassian
deleted the
ARC-1231-fix-preemptive-ratelimit-negative-number
branch
This was referenced Jun 22, 2023
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.
What's in this PR?
Fix the negative number problem.
Why
Block the sync.
Added feature flags
N/A
Affected issues
Jira Issues
How has this been tested?
Unit test.
Whats Next?
N/A