bytecodealliance / bytecodealliance/wasmtime
Write content through softlink file bug ?
- Dominant language
- Rust
- Stars
- 18.6k
- Forks
- 1.8k
- Avg merge
- 1d 18h
- Merged PRs (30d)
- 126
Description
### Test Case
The c file is uploaded as
[test-c.txt](https://github.com/bytecodealliance/wasmtime/files/13613192/test-c.txt)
The wasm file is uploaded as
[test-wasm.txt](https://github.com/bytecodealliance/wasmtime/files/13613193/test-wasm.txt)
### Steps to Reproduce
We create a normal file `Data/hello.txt`, and a softlink file `Data/link/hello_softlink.txt` points to `Data/hello.txt`
using command `wasmtime run --dir=./Data test.wasm` to execute the wasm file.
### Expected Results
In windows, WAMR could write content successfully to the source file `Data/hello.txt`. And this behavior could be considered as a right behavior, since `Data/link/hello_softlink.txt` points to `Data/hello.txt`.
### Actual Results
wasmtime create a new file `Data/link/hello.txt` and write content to this file rather the file `Data/hello.txt`.
This may be a bug?
### Versions and Environment
Wasmtime version or commit: 13.0.0
Operating system: Windows 10
Architecture: amd64
Contributor guide
Assessment
This issue has not been assessed yet.