Skip to content

Classify Node.js resolve failures via the failure framework#1687

Merged
colincasey merged 3 commits into
mainfrom
error-handling/phase-1-task-2-classify-resolve
Jul 6, 2026
Merged

Classify Node.js resolve failures via the failure framework#1687
colincasey merged 3 commits into
mainfrom
error-handling/phase-1-task-2-classify-resolve

Conversation

@colincasey

Copy link
Copy Markdown
Contributor

Continues the migration off the global ERR trap. Node.js version-resolution failures (an unresolvable version, or an invalid semver requirement) are now classified inside the runtimes::nodejs module at the point of failure, and the legacy fail_bin_install / fail_node_install / fail_invalid_semver handlers are deleted. The user-facing error text is carried over verbatim.

Second of three stacked PRs; based on #1686.

W-23231569

@colincasey colincasey self-assigned this Jun 29, 2026
@colincasey
colincasey marked this pull request as ready for review June 29, 2026 20:04
@colincasey
colincasey requested a review from a team as a code owner June 29, 2026 20:04
Base automatically changed from error-handling/phase-1-task-1-relocate-node to main July 6, 2026 13:50
…node assertion

Wrapping _install in `if ! { ... | tee }` disables errexit inside the
function body, so the bare `false` at the download and checksum failure
sites no longer aborted the install — _install fell through to tar/chmod
and could exit 0 when a stale /tmp/node.tar.gz was present. Use explicit
`return 1` so the failure propagates. Also fix the testInvalidNode stderr
assertion, which still expected the reworded "Error:" prefix after the
message was restored to its original verbatim text.
@colincasey
colincasey force-pushed the error-handling/phase-1-task-2-classify-resolve branch from 919bf0f to 71f4d8e Compare July 6, 2026 14:05
@colincasey
colincasey enabled auto-merge (squash) July 6, 2026 14:06
@colincasey
colincasey merged commit 43784fa into main Jul 6, 2026
24 checks passed
@colincasey
colincasey deleted the error-handling/phase-1-task-2-classify-resolve branch July 6, 2026 14:17
@heroku-linguist heroku-linguist Bot mentioned this pull request Jul 6, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants