-
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
__WASI_ENOENT when renaming a file #3084
Comments
Thanks for opening the issue @dicej! We'll take a look |
I reproduce the issue with current master. I'll check what's going on. |
ptitSeb
added a commit
that referenced
this issue
Aug 10, 2022
bors bot
added a commit
that referenced
this issue
Aug 10, 2022
3088: Fixed an issue when renaming a file from a preopened dir directly (for 3084) r=ptitSeb a=ptitSeb # Description Fixed an issue that could happens when renaming a file from a reopened folder Fix #3084 Co-authored-by: ptitSeb <[email protected]>
ptitSeb
added a commit
that referenced
this issue
Aug 11, 2022
…rom a preopened dir and already exist (for #3084)
bors bot
added a commit
that referenced
this issue
Aug 11, 2022
3093: Fixed a potential issue when renaming a file r=ptitSeb a=ptitSeb Fixed a potential issue when renaming a file and the destination is from a preopened dir and already exist (for #3084) Co-authored-by: ptitSeb <[email protected]>
ptitSeb
added a commit
that referenced
this issue
Oct 20, 2022
ptitSeb
added a commit
that referenced
this issue
Oct 20, 2022
…rom a preopened dir and already exist (for #3084)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
While working on konsoletyper/teavm#610, I noticed that renaming a file in a preopened directory doesn't seem to work in Wasmer. I originally noticed this when testing a Java program, but was able to reproduce it in Rust.
Wasmer complains that it doesn't understand the
-V
flag, but I'm using wasmer-cli built from commit 22c3736, which was master as of yesterday.Steps to reproduce
cargo build --target wasm32-wasi
:Expected behavior
The
foo/bar.txt
file would be renamed tofoo/um.txt
. This is the behavior when running the module using Wasmtime.Actual behavior
Error: Os { code: 44, kind: NotFound, message: "No such file or directory" }
The text was updated successfully, but these errors were encountered: