-
-
Notifications
You must be signed in to change notification settings - Fork 586
fix: Handle GitHub API rate limiting #1024
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
Open
JH-lawliet
wants to merge
6
commits into
antonbabenko:master
Choose a base branch
from
JH-lawliet:fix/1023-github-api-rate-limit
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+65
−7
Open
Changes from all commits
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
784ea86
fix(installer): handle GitHub API rate limiting
JH-lawliet f63f3c9
fix(installer): handle 403 access vs rate limit
JH-lawliet f5d6997
fix(installer): address maintainer review feedback
JH-lawliet a76da47
fix(installer): drop colorify, apply review nits
JH-lawliet f86bc01
fix(installer): pass curl command as parameter
JH-lawliet c69763f
Merge branch 'antonbabenko:master' into fix/1023-github-api-rate-limit
JH-lawliet File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Some comments aren't visible on the classic Files Changed page.
There are no files selected for viewing
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you please explain why just for the word ' (Forbidden) ' we need a whole ' if '? It does not provide any useful info, IMO, as it's literally what HTTP 403 means
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @MaxymVlasov.
For the
common::colorifyreplace, I just want to confirm that do you mean we need to copy thecolorifyfunction from thehooks/_common.sh? Because previously @yermulnik mistook the currenttools/install/_common.shforhooks/_common.shand left thecolorifycomment above. The discussion can be found hereThere was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You are right. I think there was a version that I added detailed description for
403response, but it was removed. I will remove this redundantForbiddento make it more simple.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I see. Let me quickly move colorify to a separate file so it can be easily imported everywhere
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
#1026