sakarias88 commented on Issue #2523:
@pchickey
github-actions[bot] commented on Issue #2523:
Subscribe to Label Action
cc @kubkon
<details>
This issue or pull request has been labeled: "wasi"Thus the following users have been cc'd because of the following labels:
- kubkon: wasi
To subscribe or unsubscribe from this label, edit the <code>.github/subscribe-to-label.json</code> configuration file.
Learn more.
</details>
sakarias88 commented on Issue #2523:
We will fix the CI failures once we get our hands on a windows machine.
abbec commented on Issue #2523:
"Fixing up" fstat for Windows brought a question. It seems that the fstat implementation for Windows returns a lot of OS-specific information causing a WASI
fstat
call to behave differently depending on host OS. I thought the intention was thatfstat
for example was supposed to return information from a "WASI" perspective. I.e. for example the inode number would be an "emulated" inode number that is the same on both Unix and Windows hosts (which is not the case in Wasmtime currently but it is in Wasmer)?
abbec edited a comment on Issue #2523:
"Fixing up" fstat for Windows brought a question. It seems that the fstat implementation for Windows returns a lot of OS-specific information causing a WASI
fstat
call to behave differently depending on host OS. I thought the intention was thatfstat
for example was supposed to return information from a "WASI" perspective. I.e. for example the inode number would be an "emulated" inode number that is the same on both Unix and Windows hosts (which is not the case in Wasmtime currently but it is in Wasmer)? Not that doing logic on the inode number is very likely but hey :big_smile:
abbec edited a comment on Issue #2523:
"Fixing up" fstat for Windows brought a question. It seems that the fstat implementation for Windows returns a lot of OS-specific information causing a WASI
fstat
call to behave differently depending on host OS. I thought the intention was thatfstat
for example was supposed to return information from a "WASI" perspective. I.e. for example the inode number would be an "emulated" inode number that is the same on both Unix and Windows hosts (which is not the case in Wasmtime currently but it is in Wasmer)? Not that doing logic on the inode number is very likely but anyway :big_smile:
Last updated: Dec 23 2024 at 12:05 UTC