Jimmy Bourassa (Dec 21 2022 at 18:10): Jimmy Bourassa (Dec 21 2022 at 18:10)::wave: Quick question: do y'all plan on releasing Wasmtime 4.0 before the Holiday break?
I'm debating whether I should release a new version of the Ruby gem now, or wait for 4.0 to be out.
Peter Huene (Dec 21 2022 at 18:28):I believe the plan is to go ahead with the 4.0 release this week; I think @Rainy Sinclair is the shepherd.
Jimmy Bourassa (Dec 21 2022 at 18:29):Fantastic, thanks Peter.
Peter Huene (Dec 21 2022 at 18:58):FYI: it looks like Rainy pulled the trigger and the release process has started
Rainy Sinclair (Dec 21 2022 at 18:59):release is in progress! Sorry for the delay on that.
Notification Bot (Jan 03 2023 at 20:53):Jimmy Bourassa has marked this topic as resolved.
Cwasi4wasm (Jan 18 2023 at 21:29):Sorry didn't know where to ask but I was just wondering if we have socket support in wasmtime yet?
Andrew Brown (Jan 19 2023 at 17:56):@Cwasi4wasm, I think the answer is "yes," wasi-sockets has been implemented in Wasmtime for some time (see, e.g., this PR by @Dan Gohman). You can also see what sock_* functions are available in the docs.
Cwasi4wasm (Jan 24 2023 at 12:47):Awesome thank you! I tried using Tcpstream::connect but don't think it's working. I assume it's because of how it works since I need preopened sockets
bjorn3 (Jan 24 2023 at 13:11):Indeed. You need to preopen the socket and then use TcpStream::from_raw_fd.
Cwasi4wasm (Jan 24 2023 at 20:01):Awesome thank you! Does this mean the wasm will have to know before hand where it can communicate? If I need to add a preopened socket that is
bjorn3 (Jan 25 2023 at 00:03):Yeah, that is the intention.
Last updated: Dec 23 2024 at 14:03 UTC