Fix Labeler Issue #561 - HttpError Issue #1
Closed
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
MaksimZhukov
approved these changes
May 23, 2023
|
Update: PR temporarily drafted, as the solution failed a test. I will investigate it further (and likely propose my previous solution instead, as it passes properly) |
|
I think that PR can also be closed, as this issue is most likely fixed by actions#497 with the |
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.
Description:
The changes in this PR are meant to fix the issue in Labeler that throws
HttpError: Server Errorevery time the number of labels being added exceeds a certain threshold (50+ as mentioned in the issue, but it seems to be even lower, at 48).Related issue: actions#561
Check list: