Skip to content
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

SQLite extensions test fails with error: ‘The "path" argument must be of type string. Received undefined’ #56453

Closed
Jayman2000 opened this issue Jan 3, 2025 · 1 comment

Comments

@Jayman2000
Copy link

Version

v24.0.0-pre (built from Git commit bf3bc4e)

Platform

Linux Jason-Desktop-Linux 6.12.7 #1-NixOS SMP PREEMPT_DYNAMIC Fri Dec 27 13:02:20 UTC 2024 x86_64 GNU/Linux

Subsystem

No response

What steps will reproduce the bug?

  1. Follow the instructions listed here to build Node.js from source.

  2. Change directory into the root of the node repo by running this command:

    cd <path-to-node-repo>
    
  3. Try to run the SQLite extensions test by running this command:

    out/Release/node ./test/sqlite/test-sqlite-extensions.mjs
    

How often does it reproduce? Is there a required condition?

The error happens every time for me.

What is the expected behavior? Why is that the expected behavior?

The test completes successfully.

What do you see instead?

The test prints this…

(node:31902) ExperimentalWarning: SQLite is an experimental feature and might change at any time
(Use `node --trace-warnings ...` to show where the warning was created)
node:path:1245
      validateString(arg, 'path');
      ^

TypeError [ERR_INVALID_ARG_TYPE]: The "path" argument must be of type string. Received undefined
    at Object.join (node:path:1245:7)
    at resolveBuiltBinary (file:///home/jayman/Documents/Home/VC/space_afraid/Git/partially_mine/node/space_afraid/test/sqlite/test-sqlite-extensions.mjs:17:15)
    at file:///home/jayman/Documents/Home/VC/space_afraid/Git/partially_mine/node/space_afraid/test/sqlite/test-sqlite-extensions.mjs:20:16
    at ModuleJob.run (node:internal/modules/esm/module_job:272:25)
    at async onImport.tracePromise.__proto__ (node:internal/modules/esm/loader:580:26)
    at async asyncRunEntryPointWithESMLoader (node:internal/modules/run_main:98:5) {
  code: 'ERR_INVALID_ARG_TYPE'
}

Node.js v24.0.0-pre

…and exits with exit status 1.

Additional information

No response

@Jayman2000
Copy link
Author

Jayman2000 commented Jan 5, 2025

It looks like this issue is fixed. I tried reproducing it with a newer version of the main branch (9400eae), but I wasn’t able to.

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 a pull request may close this issue.

2 participants
@Jayman2000 and others