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

Bun.serve ERR_INVALID_ARG_TYPE on Linux x64 baseline #12703

Closed
jaromanda opened this issue Jul 21, 2024 · 5 comments
Closed

Bun.serve ERR_INVALID_ARG_TYPE on Linux x64 baseline #12703

jaromanda opened this issue Jul 21, 2024 · 5 comments
Labels
bug Something isn't working needs triage

Comments

@jaromanda
Copy link

jaromanda commented Jul 21, 2024

What version of Bun is running?

v1.1.20

What platform is your computer?

Linux 6.9.7+bpo-amd64 x86_64 unknown

What steps can reproduce the bug?

Try the simple http server code from https://bun.sh/guides/http/simple

What is the expected behavior?

The server runs

What do you see instead?

1 | const server = Bun.serve({
                       ^
TypeError: 湕捩摯⁥潨瑳慮敭⁳畭瑳愠牬慥祤戠⁥湥潣敤⁤潦⁲潮⹷渊睥唠䱒椨灮瑵⸩潨瑳慮敭猠潨汵⁤潤琠敨琠楲正.敒摡扡敬瑓敲浡椠⁳湩椠癮污摩猠慴整.湉整湲污挠湯楳瑳湥祣攠牲牯›慷捴敨⁲畭整⁸獩氠捯敫⁤桷湥椠
 code: "ERR_INVALID_ARG_TYPE"

Bun v1.1.20 (Linux x64 baseline)

Additional information

The cpu has no AVX2 instruction, have installed bun Linux x64 baseline

Code works fine on "modern" cpu, but that is not an option for this VPS server.

Not sure if it's relevant, but if I cross compile i.e. using --compile=bun-linux-x64-baseline - the generated executable runs on modern cpu, but results in

error: ENOENT reading ""

On the baseline system - regardless of where I compile from (modern or baseline)

Edit: I've noticed that the above error isn't consistent

error: ENOENT reading "`x|root/baseline-app"
error: ENOENT reading "`t!root/baseline-app"
error: ENOENT reading "`Uroot/baseline-app"

Are examples of other outputs

@jaromanda jaromanda added bug Something isn't working needs triage labels Jul 21, 2024
@YANGLEDUO1
Copy link

Are you running in a virtual machine?

@jaromanda
Copy link
Author

Yes, but as I said

"Code works fine on "modern" cpu, but that is not an option for this VPS server.

@YANGLEDUO1
Copy link

The cpu type should not be recognized. I am trying to modify the correct cpu, because I also have this problem

@YANGLEDUO1
Copy link

It's my guess.

@jaromanda
Copy link
Author

This seems to be fixed with v1.1.22 - thank you

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working needs triage
Projects
None yet
Development

No branches or pull requests

2 participants