URSA-253 > Do not expect author field to contain author info in Github /commits/id response and do not try requests with 500 responses #17
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
…and do not try requests with 500 responses
ElenaHenderson
deleted the
URSA-253-do-not-expect-author-in-github-response
branch
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.
This PR:
POST /api/benchmarks/requests get 500 errors. BK builds time out (we have a 2 hour time out for BK builds) when we retry 500s.parse_committo not expectauthorfield to contain any author info in Github'sGET https://api.github.com/repos/apache/arrow/commits/idresponse.GET https://api.github.com/repos/apache/arrow/commits/idresponse sometimes hasauthor = None. This is somewhat intermittent behavior. I could not find any explanation for this but Github API users run into this issue.Here is an example of a response like this: