You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Error message from git-node v8 backport is less helpful than in node-core-utils@3.4.0 #804
Attempted to backport a commit that doesn't exist yet.
With node-core-utils@3.4.0:
$ npx --package=node-core-utils@3.4.0 -- git-node v8 backport df5724c11697b4fbe803adcb5a51020dea2d923fNeed to install the following packages:node-core-utils@3.4.0Ok to proceed? (y) ynpm WARN deprecated node-core-utils@3.4.0: This package has been renamed to @node-core/utils(node:1406084) [DEP0040] DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead.(Use `node --trace-deprecation ...` to show where the warning was created)✔ Update local V8 clone⠦ V8 commit backportfatal: ambiguous argument 'df5724c11697b4fbe803adcb5a51020dea2d923f^..df5724c11697b4fbe803adcb5a51020dea2d923f': unknown revision or path not in the working tree.Use '--' to separate paths from revisions, like this:'git <command> [<revision>...] -- [<file>...]'fatal: ambiguous argument 'df5724c11697b4fbe803adcb5a51020dea2d923f': unknown revision or path not in the working tree.Use '--' to separate paths from revisions, like this:'git <command> [<revision>...] -- [<file>...]'
$
With @node-core/utils@5.0.1:
$ npx --package=@node-core/utils@latest -- git-node v8 backport df5724c11697b4fbe803adcb5a51020dea2d923fNeed to install the following packages:@node-core/utils@5.0.1Ok to proceed? (y) y✔ Update local V8 clone
❯ V8 commit backport ✔ Get current V8 version ✔ Generate patches ❯ Apply and commit patches to deps/v8 ❯ Commit df5724c11697 ✔ Apply patch ✔ Increment embedder version number ✖ Cannot read properties of undefined (reading 'replace')✖ Cannot read properties of undefined (reading 'replace')
$
The error from the older version is a lot more indicative of what the actual problem is.
changed the title [-]Error message from `git-node v8 backport` is less helpful that in node-core-utils@3.4.0[/-][+]Error message from `git-node v8 backport` is less helpful than in node-core-utils@3.4.0[/+]on May 1, 2024
The git format-patch command should fail (with error message matching that from node-core-utils@3.4.0):
$ pwd/home/rlau/.update-v8/v8
$ git format-patch --stdout df5724c11697b4fbe803adcb5a51020dea2d923f^..df5724c11697b4fbe803adcb5a51020dea2d923ffatal: ambiguous argument 'df5724c11697b4fbe803adcb5a51020dea2d923f^..df5724c11697b4fbe803adcb5a51020dea2d923f': unknown revision or path not in the working tree.Use '--' to separate paths from revisions, like this:'git <command> [<revision>...] -- [<file>...]'
$ echo$?128
$
I couldn't seem to get NCU_VERBOSITY to output any extra info with node-core-utils@3.4.0.
I tried with this patch:
Activity
[-]Error message from `git-node v8 backport` is less helpful that in node-core-utils@3.4.0[/-][+]Error message from `git-node v8 backport` is less helpful than in node-core-utils@3.4.0[/+]targos commentedon May 1, 2024
It looks like the expected error doesn't happen anymore, or is somehow swallowed.
richardlau commentedon May 1, 2024
I guess maybe being swallowed?
The
git format-patchcommand should fail (with error message matching that from node-core-utils@3.4.0):I couldn't seem to get
NCU_VERBOSITYto output any extra info with node-core-utils@3.4.0.I tried with this patch:
but this still doesn't capture the error (note the debug output shows that
inheritis being used):richardlau commentedon May 1, 2024
Neither does changing to
pipe:targos commentedon May 12, 2024
#809 may help.