-
Notifications
You must be signed in to change notification settings - Fork 31.2k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
util.inspect fails in some border conditions with an argument that has a name
#56570
Labels
util
Issues and PRs related to the built-in util module.
Comments
ljharb
added a commit
to ljharb/node
that referenced
this issue
Jan 12, 2025
ljharb
added a commit
to ljharb/node
that referenced
this issue
Jan 12, 2025
ljharb
added a commit
to ljharb/node
that referenced
this issue
Jan 12, 2025
ljharb
added a commit
to ljharb/node
that referenced
this issue
Jan 12, 2025
#56574 should address regExpName |
@ljharb ☀️ |
ljharb
added a commit
to ljharb/node
that referenced
this issue
Jan 13, 2025
ljharb
added a commit
to ljharb/node
that referenced
this issue
Jan 13, 2025
ljharb
added a commit
to ljharb/node
that referenced
this issue
Jan 13, 2025
ljharb
added a commit
to ljharb/node
that referenced
this issue
Jan 15, 2025
ljharb
added a commit
to ljharb/node
that referenced
this issue
Jan 15, 2025
ljharb
added a commit
to ljharb/node
that referenced
this issue
Jan 15, 2025
wongprom
pushed a commit
to wongprom/node
that referenced
this issue
Jan 15, 2025
See nodejs#56570 PR-URL: nodejs#56574 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Matthew Aitken <maitken033380023@gmail.com> Reviewed-By: Marco Ippolito <marcoippolito54@gmail.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de>
ljharb
added a commit
to ljharb/node
that referenced
this issue
Jan 22, 2025
ljharb
added a commit
to ljharb/node
that referenced
this issue
Jan 22, 2025
ljharb
added a commit
to ljharb/node
that referenced
this issue
Jan 22, 2025
ljharb
added a commit
to ljharb/node
that referenced
this issue
Jan 23, 2025
hvanness
pushed a commit
to hvanness/node
that referenced
this issue
Jan 30, 2025
See nodejs#56570 PR-URL: nodejs#56573 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: Jason Zhang <xzha4350@gmail.com> Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de>
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
Version
v22.10.0
Platform
Subsystem
node:util
What steps will reproduce the bug?
util.inspect
, as I understand it, is supposed to work in all conditions, whatever we throw at it. The code below shows 19 cases whereutil.inspect
fails:How often does it reproduce? Is there a required condition?
Reproducible with the above code.
What is the expected behavior? Why is that the expected behavior?
util.inspect
, as I understand it, is supposed to work and return a string in all conditions, whatever we throw at it.What do you see instead?
symbolName
symbolName
represents 9 failing cases, where the object argument toutil.inspect
is anError
or a function, with asymbol
as aname
complexArrayName
complexArrayName
represents 9 failing cases, where the object argument toutil.inspect
is anError
or a function, with an array that contains asymbol
as aname
(note that using an object with a property that has asymbol
value works as expected)regExpName
regExpName
represents 1 failing case, where the object argument toutil.inspect
is anError
with aRegExp
as aname
Additional information
No response
The text was updated successfully, but these errors were encountered: