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

Windows version crashes with invalid path parameters value #924

Closed
mountaindude opened this issue Oct 21, 2024 · 1 comment · Fixed by #910 · May be fixed by #936
Closed

Windows version crashes with invalid path parameters value #924

mountaindude opened this issue Oct 21, 2024 · 1 comment · Fixed by #910 · May be fixed by #936
Labels

Comments

@mountaindude
Copy link
Collaborator

What version of Butler SOS are you using?

11.0.1

What version of Node.js are you using? Not applicable if you use the standalone version of Butler SOS.

No response

What command did you use to start Butler SOS?

.\butler-sos.exe --configfile .\butler-sos-config-influx2.yaml --loglevel info

What operating system are you using?

Windows server 2019

What CPU architecture are you using?

x86_64

What Qlik Sense versions are you using?

2024-May IR

Describe the Bug

When starting on Windows I get this error:

PS C:\tools\butler-sos> .\butler-sos.exe --configfile .\butler-sos-config-influx2.yaml
node:internal/errors:477
    ErrorCaptureStackTrace(err);
    ^

TypeError [ERR_INVALID_ARG_TYPE]: The "path" argument must be of type string or an instance of URL. Received undefined
    at new NodeError (node:internal/errors:388:5)
    at fileURLToPath (node:internal/url:1486:11)
    at t.init (C:\snapshot\butler-sos\build.cjs:800:4622)
    at process.runNextTicks [as _tickCallback] (node:internal/process/task_queues:60:5)
    at Function.runMain (pkg/prelude/bootstrap.js:1980:13)
    at node:internal/main/run_main_module:17:47
    at async IHt (C:\snapshot\butler-sos\build.cjs:1076:158302) {
  code: 'ERR_INVALID_ARG_TYPE'
}

Node.js v18.5.0
PS C:\tools\butler-sos>

Starting on macOS or using plain Node.js does NOT give this error.

Expected Behavior

No response

To Reproduce

No response

@mountaindude
Copy link
Collaborator Author

Most likely caused by --inject:./src/lib/import-meta-url.js --define:import.meta.url=import_meta_url missing in the ci.yaml GitHub Actions workflow (which builds release binaries).

Those parameters are present in the insiders-build.yaml file, which would explain why those binaries worked.

Testing hypothesis before closing ticket.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
1 participant