Fix NullPointerException on RateLimitHandler when handling API errors. #179
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.
Hello!
We encountered a NullPointerException after the upgrade to 1.67 when rate limited by the GitHub API. Essentially it is because the call to
getMyself().getLogin()
failed during the construction of the GitHub object due to being rate limited. However, the RateLimitHandler object had not yet been set at that point in time within the GitHub object constructor. Fix is a simple statement movement.Error within GitHub::handleApiError():
Ran the test suite locally after setting github authentication details:
Failures seem to be mostly related to access to the github-api-test-org (which obviously I don't have any permissions for), and I had the same results before/after the change so it looks like they are unrelated to it - Hopefully that's acceptable!
Thanks,
Lee