Yage Hu

I just spent 2 hours tearing my hairs out. My project worked fine with serde_json *without* `arbitrary_precision`. Then I added [tracing-bunyan-formatter](https://github.com/LukeMathWalker/tracing-bunyan-formatter) which enables this feature to my project and all...

I'm curious about the status of threads for WASI as well. Is there a timeline? How do I find out more about the process? I'm new sorry if this is...

Also need to escape characters like `?` and `*`

I'm noticing the same behavior occasionally. I'm working with similarly sized Rust files (hundreds of lines) in a repository of dozens of source files. I'm on amd64 darwin.

Definitely a Linux bug as you linked. It was [first raised by Micharl Kerrisk](https://bugzilla.kernel.org/show_bug.cgi?id=43178). You can argue WASI aims to be platform independent, so a specification compliant implementation should fix...

I did some digging and found that Wasmtime solves it in preview1 by managing the append flag and hiding it from the underlying syscall. It has nothing to do with...

@hydai Test case submitted: https://github.com/WebAssembly/wasi-testsuite/pull/95

Since this is a Linux behavior, it would be hard to fix without emulating the WASI fs layer. I will close this as wontfix & stale. If the maintainers wish...

A quick update since there's interest in fixing this. On darwin in the absence of the Linux pwrite/append bug, Wasmtime, Wasmer, WAMR, and Node all behave as expected (pwrite over...

@hydai Can you look at #3390? It implements the fix for Darwin. Currently, WasmEdge is the only runtime that ignores the `pwrite` offset on Darwin.