water icon indicating copy to clipboard operation
water copied to clipboard

WebAssembly Transport Executables Runtime

Results 12 water issues
Sort by recently updated
recently updated
newest added

Since WATM v1 driver is already implemented and merged in #65, we should update README.md and any other related documentation to reflect the change we have made to introduce the...

documentation
good first issue

It is feasible to include a standalone testing package for [watm](https://github.com/refraction-networking/watm) to be run for every newly created WATM. This also helps with the CI/CD pipeline of the watm repository...

enhancement

WASI Preview 2, aka WASI 0.2.0 is now stable. It would greatly benefit this project by introducing official `wasi-sockets` support. We should evaluate WASI Preview 2 and its support from...

enhancement

Hi there, congratulations on getting this project to this state, it looks quite promising! As part of the development of Outline and [Outline SDK](https://github.com/Jigsaw-Code/outline-sdk), I played with interfaces a lot....

enhancement

WATM v1 spec is getting close to be finalized and once merged, will be replacing former WATM specifications (`v0` and former `v1`-preview will be removed). This repository should start implementing...

Still work in progress. - [x] Use newly build `io/pipe` package - [ ] use vendor package instead of introducing an external dependency - [ ] Use updated WATM v1...

## Problem If the `ctx` used in `DialContext` is cancelled AFTER the function returns, the returned `water.Conn` will be closed. See https://github.com/hwh33/water-context-bug for an example. ## Cause Two causes contributed...

bug
enhancement

One of the external dependency of `water`, `tetratelabs/wazero` has been replaced with our fork, `refraction-networking/wazero`. However, Go itself will not inherit the `replace` directive in `go.mod` and therefore any dependents...

documentation
help wanted
question

Currently both `transport/v0` and `transport/v1` hardcodes `TCPConn` for local WASI usage (caller WATM) and `UnixConn` is unused. It would be potentially interesting to allow the use of `UnixConn` by caller's...

enhancement
wontfix

Requesting insights on performance between `UnixConn` and `TCPConn` under different scenarios. --- Is the prerequisite of: #68

question