You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 16, 2020. It is now read-only.
For some code I am generating using C++ and Emscripten, it is very hard to prevent emscripten from adding imports of the "fd_read" and "fd_fdstat_get" functions. I would like to add them to the WASI implementation in Envoy.
I already have a PR and these functions work:
fd_read always returns "EBADF"
fd_fdstat_get returns "EBADF" for anything other than fds 1 and 2 -- since we already allow code to write to those fds using fd_write, the implementation returns a reasonable response for those.
Before I submit a PR, I'd like to know what a reasonable testing strategy is. I'd be willing to attempt a stand-alone unit test for the WASI support in Envoy. Would that be helpful?
The text was updated successfully, but these errors were encountered:
gbrail
added a commit
to gbrail/envoy-wasm
that referenced
this issue
Feb 25, 2020
fd_read: Always returns EBADF
fd_fdstat_get: Returns a reasonable response for fds 0 and 1,
and EBADF otherwise.
Add a "WASI" test configuration to the existing tests that checks
for proper implementation of these by testing "fprintf,"
"fread," and "isatty".
Fixesenvoyproxy#425
Signed-off-by: Gregory Brail <gregbrail@google.com>
fd_read: Always returns ENOSYS
fd_fdstat_get: Returns a reasonable response for fds 0 and 1,
and EBADF otherwise.
Add a "WASI" test configuration to the existing tests that checks
for proper implementation of these by testing "fprintf,"
"fread," and "isatty".
Fixes#425
Signed-off-by: Gregory Brail <gregbrail@google.com>
fd_read: Always returns ENOSYS
fd_fdstat_get: Returns a reasonable response for fds 0 and 1,
and EBADF otherwise.
Add a "WASI" test configuration to the existing tests that checks
for proper implementation of these by testing "fprintf,"
"fread," and "isatty".
Fixesenvoyproxy/envoy-wasm#425
Signed-off-by: Gregory Brail <gregbrail@google.com>
Signed-off-by: Piotr Sikora <piotrsikora@google.com>
For some code I am generating using C++ and Emscripten, it is very hard to prevent emscripten from adding imports of the "fd_read" and "fd_fdstat_get" functions. I would like to add them to the WASI implementation in Envoy.
I already have a PR and these functions work:
fd_read always returns "EBADF"
fd_fdstat_get returns "EBADF" for anything other than fds 1 and 2 -- since we already allow code to write to those fds using fd_write, the implementation returns a reasonable response for those.
Before I submit a PR, I'd like to know what a reasonable testing strategy is. I'd be willing to attempt a stand-alone unit test for the WASI support in Envoy. Would that be helpful?
The text was updated successfully, but these errors were encountered: