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.
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
util: limit inspection output size to 128 MB #22756
util: limit inspection output size to 128 MB #22756
Changes from all commits
dbb2b1a
8742df1
b1cb015
e133551
0dde647
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I get wanting to limit string construction to avoid memory issues and it looks like when this is implemented objects just won't be crawled (something like
"[Object]"
) which are both good.Am I correct that the indentation level is just a hint that there could be a possible problem (it's unknown until the objects are crawled and inspected) and so it's being defensive and not going further?
Can indentation level be translated to depth?
(I think depth would be easier to reason about at a glance than indenting)
Can an object still be created that busts this heuristic?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
depth
is not possible though, as it's value is set by the user (e.g., toInfinity
), not byinspect()
itself.indentationLvl
is only meant to be internal and is never set toInfinity
.util.inspect(new Uint8Array(1e8), { maxArrayLength: Infinity })
. If an individual part of an object exceeds the limit on it's own or the total space left, it's not going to protect against it.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looking at this again: the
depth
and theindentationLvl
would be great to be combined but thecompact: true
mode has different indention for different values. That's why it's currently not possible :/There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That's cool. This is a good first attempt at least.