WASI fd_read from stdin works once (blocks) then immediately returns about lucet HOT 3 CLOSED

Hi,

And sorry for the delayed response.

      (drop (call $fd_write (i32.const 0) (i32.const 16) (i32.const 1) (i32.const 256)))

The descriptor should probably be 1, not 0 here.

That being said, what happens here is that __wasi_fd_read(0...) returns __WASI_EBADF after the first read. This should obviously not be the case.

It only happens when stdin in a TTY. With a file, the descriptor remains valid.

I'm going to investigate why this happens. Thanks for your report!

from lucet.

@jedisct1 ah yes, I think that must have been a copy/paste from the previous line and I forgot to update the fd value. Thanks for looking into it.

For a little context, I'm trying to get the webassembly implementation of mal/make-a-lisp working across several runtimes. I've gotten it running in wasmtime and in my own runtimes (wac and warpy) but this was one of the issues I ran into trying to get it to run under lucet.

from lucet.

@jedisct1 I've built lucet with the change and confirmed that it is fixed for my use case. Now on to the next problem I discovered with mal/make-a-lisp: #158 :-)

from lucet.