-
Notifications
You must be signed in to change notification settings - Fork 824
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
Still fail to get the file discriptor? #4778
Comments
I figured out the difference in our setup. With |
This may be related to #4245 |
We checked different OS permission with different openstyle, and found that wasmer is different from other WASM runtimes, including wasmtime, WAMR and WasmEdge. wasmer version 4.3.1(1)It should have successfully obtained the file descriptor, but it failed.DIRNAME->0700 FILENAME->0600 FILENAME->0200 FILENAME->0600 FILENAME->0600 FILENAME->0600 FILENAME->0600 DIRNAME->0500 DIRNAME->0600 FILENAME->0600 FILENAME->0600 FILENAME->0200 FILENAME->0200 FILENAME->0600 DIRNAME->0400 FILENAME->0600 FILENAME->0200 FILENAME->0600 FILENAME->0200 FILENAME->0600 FILENAME->0400 (2)It should not have successfully obtained the file descriptor, but it succeeded.FILENAME->0400 FILENAME->0400 FILENAME->0400 FILENAME->0200 FILENAME->0200 FILENAME->0400 wasmer version 4.2.2(1)It should have successfully obtained the file descriptor, but it failed.FILENAME->0400 (2)It should not have successfully obtained the file descriptor, but it succeeded.DIRNAME->0100 DIRNAME->0300 DIRNAME->0200 |
This is related to #4753, which may not be resolved.
The text was updated successfully, but these errors were encountered: