chore: tweak max_ancestors_count #4487
Merged
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
eval-exec
previously approved these changes
Jun 20, 2024
quake
previously approved these changes
Jun 20, 2024
|
I remember this case also need to fix: |
zhangsoledad
force-pushed
the
zhangsoledad/tweak_max_ancestors_count
branch
from
fe98cff to
6619344
Compare
eval-exec
approved these changes
Jun 20, 2024
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.
What problem does this PR solve?
The current limitation of max_ancestors is too small and affects many application scenarios. After retesting, we have adjusted max_ancestors to a more appropriate yet safe value.
Related changes
owner/repo:Check List
Tests
Side effects
Release note