Increase MAX_PARSING_DEPTH to 512 #3158
Closed
Conversation
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
|
Hello, there is #3063 that hopefully can get merged at some point |
|
ack, thanks.
|
itchyny
added a commit
to itchyny/jq
that referenced
this pull request
May 29, 2025
This is the same limit of encoding/json package in Go. Closes jqlang#2846, closes jqlang#3158, and addresses jqlang#1214.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
To, I hit error
parse error: Exceeds depth limit for parsingon reasonable JSON files in production.This PR fixes this limitation.