-
Notifications
You must be signed in to change notification settings - Fork 29.8k
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: display a present-but-undefined error cause #41247
util: display a present-but-undefined error cause #41247
Conversation
29c7b48
to
eb46007
Compare
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.
Firefox output is:
Error: undefined cause
<anonymous> debugger eval code:1
Caused by: undefined
This comment has been minimized.
This comment has been minimized.
eb46007
to
d318e47
Compare
What's next to land this? :-) |
Commit Queue failed- Loading data for nodejs/node/pull/41247 ✔ Done loading data for nodejs/node/pull/41247 ----------------------------------- PR info ------------------------------------ Title util: display a present-but-undefined error cause (#41247) ⚠ Could not retrieve the email or name of the PR author's from user's GitHub profile! Branch ljharb:util-inspect-undefined-cause -> nodejs:master Labels util, author ready, needs-ci Commits 1 - util: display a present-but-undefined error cause Committers 1 - Jordan Harband PR-URL: https://github.com/nodejs/node/pull/41247 Reviewed-By: Antoine du Hamel Reviewed-By: Colin Ihrig Reviewed-By: Michaël Zasso Reviewed-By: Ruben Bridgewater Reviewed-By: Luigi Pinca ------------------------------ Generated metadata ------------------------------ PR-URL: https://github.com/nodejs/node/pull/41247 Reviewed-By: Antoine du Hamel Reviewed-By: Colin Ihrig Reviewed-By: Michaël Zasso Reviewed-By: Ruben Bridgewater Reviewed-By: Luigi Pinca -------------------------------------------------------------------------------- ℹ This PR was created on Sun, 19 Dec 2021 23:34:01 GMT ✔ Approvals: 5 ✔ - Antoine du Hamel (@aduh95) (TSC): https://github.com/nodejs/node/pull/41247#pullrequestreview-835919665 ✔ - Colin Ihrig (@cjihrig) (TSC): https://github.com/nodejs/node/pull/41247#pullrequestreview-835922609 ✔ - Michaël Zasso (@targos) (TSC): https://github.com/nodejs/node/pull/41247#pullrequestreview-836065279 ✔ - Ruben Bridgewater (@BridgeAR) (TSC): https://github.com/nodejs/node/pull/41247#pullrequestreview-836157757 ✔ - Luigi Pinca (@lpinca): https://github.com/nodejs/node/pull/41247#pullrequestreview-836782076 ✖ This PR needs to wait 26 more hours to land ✔ Last GitHub Actions successful ℹ Last Full PR CI on 2021-12-20T08:37:03Z: https://ci.nodejs.org/job/node-test-pull-request/41555/ - Querying data for job/node-test-pull-request/41555/ ✔ Last Jenkins CI successful -------------------------------------------------------------------------------- ✔ Aborted `git node land` session in /home/runner/work/node/node/.ncuhttps://github.com/nodejs/node/actions/runs/1603912136 |
|
@targos aha, thanks :-) i'll wait out the time then |
It's now been 26 hours since that failure; would someone mind kicking off the commit queue? 🙏 |
✖ This PR needs to wait 21 more minutes to land |
Landed in 8d1f13b |
Thanks everyone! |
Can/should this get the backport requested label for node 17? |
@ljharb adding that label is an indicator that there's need for a manual backport and it won't be pulled in automatically anymore. As a patch, it is likely to be pulled into the next releases that contain the basic implementation. |
See #41097 (comment) PR-URL: #41247 Reviewed-By: Antoine du Hamel <[email protected]> Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: Michaël Zasso <[email protected]> Reviewed-By: Ruben Bridgewater <[email protected]> Reviewed-By: Luigi Pinca <[email protected]> Reviewed-By: Tobias Nießen <[email protected]> Reviewed-By: James M Snell <[email protected]>
See #41097 (comment) PR-URL: #41247 Reviewed-By: Antoine du Hamel <[email protected]> Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: Michaël Zasso <[email protected]> Reviewed-By: Ruben Bridgewater <[email protected]> Reviewed-By: Luigi Pinca <[email protected]> Reviewed-By: Tobias Nießen <[email protected]> Reviewed-By: James M Snell <[email protected]>
See nodejs#41097 (comment) PR-URL: nodejs#41247 Reviewed-By: Antoine du Hamel <[email protected]> Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: Michaël Zasso <[email protected]> Reviewed-By: Ruben Bridgewater <[email protected]> Reviewed-By: Luigi Pinca <[email protected]> Reviewed-By: Tobias Nießen <[email protected]> Reviewed-By: James M Snell <[email protected]>
See #41097 (comment) PR-URL: #41247 Reviewed-By: Antoine du Hamel <[email protected]> Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: Michaël Zasso <[email protected]> Reviewed-By: Ruben Bridgewater <[email protected]> Reviewed-By: Luigi Pinca <[email protected]> Reviewed-By: Tobias Nießen <[email protected]> Reviewed-By: James M Snell <[email protected]>
See #41097 (comment)
It was a very explicit and intentional decision to differentiate an
undefined
cause from an absent cause, so let's display it.cc @nodejs/util