-
-
Notifications
You must be signed in to change notification settings - Fork 358
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
Unexpected removal of function name from node:internal frame in stack trace #1589
Comments
Krinkle
added a commit
to Krinkle/sandbox
that referenced
this issue
Jan 24, 2025
Krinkle
added a commit
to Krinkle/sandbox
that referenced
this issue
Jan 24, 2025
Krinkle
added a commit
to Krinkle/sandbox
that referenced
this issue
Jan 24, 2025
Krinkle
added a commit
to Krinkle/sandbox
that referenced
this issue
Jan 24, 2025
Krinkle
added a commit
to Krinkle/sandbox
that referenced
this issue
Jan 24, 2025
Krinkle
added a commit
to Krinkle/sandbox
that referenced
this issue
Jan 24, 2025
Krinkle
added a commit
to Krinkle/sandbox
that referenced
this issue
Jan 24, 2025
Krinkle
added a commit
to Krinkle/sandbox
that referenced
this issue
Jan 24, 2025
Krinkle
added a commit
to Krinkle/sandbox
that referenced
this issue
Jan 24, 2025
In case it is specific to some versions or OS, I pulled an isolated example through GitHub CI at
https://github.com/Krinkle/sandbox/actions/runs/12945508832/job/36108207401 It seems specific to Node.js 22 and later. On Node.js 20 the affected frame looked like this:
which is left alone. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Node.js v23.6.0
nyc 17.1.0
The corrupted line in question is:
which nyc turns into
thus the
at functionName (path/file)
formatting structure, and becomingat path/file
instead.This caused a very minor issue in a project with strict output fixtures that, despite various normalization layers, failed to match with NYC enabled because it was unable to parse those lines correctly.
https://github.com/qunitjs/qunit/blob/3.0.0-alpha.4/test/cli/helpers/execute.js#L35-L53
The text was updated successfully, but these errors were encountered: