[SPARK-46811][FOLLOWUP] Increase check_run response result from 30 to 100#44862
Closed
yaooqinn wants to merge 1 commit intoapache:masterfrom
Closed
[SPARK-46811][FOLLOWUP] Increase check_run response result from 30 to 100#44862yaooqinn wants to merge 1 commit intoapache:masterfrom
yaooqinn wants to merge 1 commit intoapache:masterfrom
Conversation
dongjoon-hyun
approved these changes
Jan 24, 2024
HyukjinKwon
approved these changes
Jan 24, 2024
Member
|
Merged to master. |
Member
Author
|
Thank you @dongjoon-hyun @HyukjinKwon |
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
3 participants
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.
What changes were proposed in this pull request?
This PR increases check_run response results from 30 to 100 to prevent
Run / Check changesfrom missing in the response.Why are the changes needed?
Although the type error is fixed, we still see retry failures when calling the check_run API
Does this PR introduce any user-facing change?
no
How was this patch tested?
Use
to test
Was this patch authored or co-authored using generative AI tooling?
no