Skip to content
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.

Sign up for GitHub

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

Jump to bottom

WASI.fork() #66

Closed
npmccallum opened this issue Mar 27, 2019 · 3 comments
Closed

WASI.fork() #66

npmccallum opened this issue Mar 27, 2019 · 3 comments
Labels
wasi:api Issues pertaining to the WASI API, not necessarily specific to Wasmtime.

Comments

@npmccallum
Copy link
Member

Please move WASI to a separate repository. I'm interested in being a contributor to WASI, but not necessarily to wasmtime. It would be good to discuss the standard independently from the implementation.
@sunfishcode sunfishcode added the wasi:api Issues pertaining to the WASI API, not necessarily specific to Wasmtime. label Mar 27, 2019
@sunfishcode
Copy link
Member

I have an agenda item in the next WebAssembly CG meeting to propose a CG Subgroup for the next steps of WASI's evolution and eventual standardization. If this is accepted, then we'll set up a dedicated repository for WASI within the WebAssembly organization. If not, we'll look into other options.

Until then, I'd prefer not to create another temporary home. I created a WASI issue label in this repository so that we can mark issues and PRs pertaining to WASI, which hopefully sufficies until the real home is ready.

@sunfishcode
Copy link
Member

Here's a link to quickly show all WASI-specific issues.

@sunfishcode
Copy link
Member

The CG subgroup is now approved. The dedicated github repo is here. We'll be migrating content over soon, but for now the issue tracker is at least open.

howjmay pushed a commit to howjmay/wasmtime that referenced this issue Jan 24, 2022
@alexcrichton
Bind more Wasmtime-specific APIs on Linker (bytecodealliance#67)
e15ef13 
Closes bytecodealliance#66
pchickey pushed a commit to pchickey/wasmtime that referenced this issue May 16, 2023
@sunfishcode
On Windows, ignore access-denied errors from sync_all. (bytecodeall…
479661d 
…iance#67)

* On Windows, ignore access-denied errors from `sync_all`.

On Windows `sync_all` does `FlushFileBuffers` which fails with an
access-denied error if the file not opened for writing. Ignore this
error, for compatibility with POSIX-style APIs.

Fixes bytecodealliance#66.

* Ignore `ERROR_ACCESS_DENIED` from `sync_data` too.

* Temporarily disable directory syncing for now.
dhil added a commit to dhil/wasmtime that referenced this issue Dec 13, 2023
@dhil
Merge pull request bytecodealliance#66 from dhil/wasmfx-merge
6ed3e1d 
Merge with upstream
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
wasi:api Issues pertaining to the WASI API, not necessarily specific to Wasmtime.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@npmccallum @sunfishcode