Repository navigation
Dependency updates: retry the API when dev has only just moved (version 0.4.8) - #54
Merged
Merged
Conversation
…n't know dev's newest commit yet (version 0.4.8)
Merged
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
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.
Task 4f follow-up.
After #53 merged, the update run started three seconds later and GitHub's API answered
base_tree is not a valid tree oid(HTTP 422) for dev's brand-new merge commit, so #48 was held. A minute later the same path worked for #49: its version commit is signed by GitHub (verified: true, committer web-flow), which is what #53 was for. #49 was then held because build failed on it (Selenium 4.1 to 4.51 removedScreenshotImageFormat), as designed.Each API call is now tried up to four times, 15 seconds apart.
Version 0.4.8, heading only. Self-test 17 of 17.