-
Notifications
You must be signed in to change notification settings - Fork 27
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
when i new evidence project , it shows node FATAL ERROR: v8::Template::Set Invalid value, must be a primitive or a Template ----- Native stack trace ----- #103
Comments
node test.js 1: 0x104d88b18 node::OnFatalError(char const*, char const*) [/Users/yi/.nvm/versions/node/v20.15.0/bin/node] ----- JavaScript stack trace ----- 1: Module._extensions..node (node:internal/modules/cjs/loader:1454:18) zsh: abort node test.js |
Could you try again, with the same workflow as evidence-dev/evidence#2146 (comment), but with two twists:
(and copy pasting the log, that for me looks like:
And then going further with the other steps. Otherwise:
(this will take a while) |
Hey, thanks for reporting, will have another look. |
I had the same issue that @taste1989 was reporting except that I was running on an intel mac (don't ask,lol) . Noticed that npm uninstall duckdb does not delete duckdb and duckdb-async dirs from node_modules. Went ahead and manually deleted folders. Installed from source as noted above. That took care of the issue. |
@taste1989 / @arungk : I am having a hard time reproducing this, which VSCode versions are you at? Or even better, can you reproduce outside of VSCode? I have found this VSCode issue: microsoft/vscode#219893 that might be somehow related, although I can't understand how the workaround would solve it here. |
@archiewood: sorry for spamming, but I am not super comfortable with this issue, and was wondering if you could take another look. Basically what I am observing is that however a module is (badly) built, it should not allow node to throw FATAL_ERROR, so I am thinking this is likely a problem on tooling that looks to be out of our (duckdb) control. If you have any feedback or suggested line of action, it would be very welcome. Thanks |
Hey @carlopi - why is VSCode relevant here? is this not all happening from the command line? @taste1989 can you clarify what you mean by "in vscode" |
hi I report this issue evidence-dev/evidence#2146 in evidence. archiewood told me to report here.
The text was updated successfully, but these errors were encountered: