unset max_value_len when parsing LSP messages #1437
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
Techatrix
force-pushed
the
max-json-value-len
branch
2 times, most recently
from
3f68ce3 to
2109f25
Compare
leecannon
approved these changes
Sep 16, 2023
leecannon
force-pushed
the
max-json-value-len
branch
from
2109f25 to
95c87b8
Compare
KoltPenny
pushed a commit
to KoltPenny/zls
that referenced
this pull request
Oct 18, 2023
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.
turns out, ZLS can't open a file over 4Mb.
Yes, I am looking at you
zig/lib/compiler_rt/udivmodti4_test.zigdepends on ziglang/zig#17107TODO: update nix flake