Reduce default CHALK_SOLVER_MAX_SIZE to 100#11884
Closed
ivan wants to merge 1 commit into
Closed
Conversation
Contributor
|
Keeping the max size the same but increasing the max depth did not solve your problem? |
Contributor
Author
|
That's right. With the test repo in #11370 (comment) and I still see these errors from rust-analyzer:
|
Contributor
|
☔ The latest upstream changes (presumably #12118) made this pull request unmergeable. Please resolve the merge conflicts. |
Contributor
|
☔ The latest upstream changes (presumably #12281) made this pull request unmergeable. Please resolve the merge conflicts. |
Member
|
I've increased |
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.
This fixes #11370. Please see the investigation in #11370 (comment).
CHALK_SOLVER_MAX_SIZEneeds to be high enough to deduce types (see #11072), but not so high as to cause "server panicked: overflow depth reached" (#11370)