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

Tokio panic when running lavarel locally #5344

Open
linear bot opened this issue Jan 14, 2025 · 1 comment
Open

Tokio panic when running lavarel locally #5344

linear bot opened this issue Jan 14, 2025 · 1 comment
Labels
bug Something isn't working

Comments

@linear
Copy link

linear bot commented Jan 14, 2025

I suspect this is a 'works on my machine' issue, but anyways.

Follow the steps:

  • cd $(mktemp -d)
  • composer create-project laravel/laravel wasmer-edge-laravel
  • cd wasmer-edge-laravel
  • copy toml from 'docs.wasmer.io/edge/guides/laravel#setup-a-wasmer-package'
  • wasmer run .
  • (in seprate terminal) curl localhost:8080

I get this:

Γ¥» wasmer run .
The current package is requesting networking access.
Run the package with `--net` flag to bypass the prompt.
? Would you like to allow networking for this package? [options: yes/no/always] (alwa
Γ£ö Would you like to allow networking for this package? [options: yes/no/always] ┬╖ always
[Tue Jan 14 04:46:47 2025] PHP 8.3.4 Development Server (http://localhost:8080) started
[Tue Jan 14 04:46:51 2025] 127.0.0.1:48856 Accepted
thread 'TokioTaskManager Thread Pool_thread_2' panicked at lib/virtual-fs/src/host_fs.rs:483:63:
called `Result::unwrap()` on an `Err` value: Os { code: 24, kind: Uncategorized, message: "Too many open files" }
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
error: Unable to wait for the process to exit
Γöé   1: RuntimeError: Thread manager disconnected
Γöé   2: RuntimeError: Thread manager disconnected
Γò░ΓöÇΓû╢ 3: Thread manager disconnected

Wasmer version 5.0.4

Running WSL2 ubuntu 22.04

@linear linear bot added bug Something isn't working wasix and removed wasix labels Jan 14, 2025
@syrusakbary
Copy link
Member

The "Too many open files" can be solved by doing ulimit -n 10240 or similar.

We'll need to refactor the WASIX FS to properly fix this issue I believe

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

No branches or pull requests

1 participant