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
I stumbled across a data race that appears to happen when you try to perform concurrent actions against one (or more) patterns.
It's unclear whether this stems from this library or https://github.com/tetratelabs/wazero as I see read/write warnings for both. Normally I'd try to provide helpful speculation about the cause, however, this goes a bit over my head.
Hi @rgmz - thanks for the report. Wasm is tricky in that even if it correctly locks within the compiled code, the Go race detector doesn't know about it and can produce warnings as a result. But either way probably Go apps do need to be able to pass with the race detector when using wazero. One race was within this library code which I fixed in #126 but the others seem to be within wazero. I filed tetratelabs/wazero#2278 to see if we can work around it. Sorry for the trouble.
I stumbled across a data race that appears to happen when you try to perform concurrent actions against one (or more) patterns.
It's unclear whether this stems from this library or https://github.com/tetratelabs/wazero as I see read/write warnings for both. Normally I'd try to provide helpful speculation about the cause, however, this goes a bit over my head.
Data race warnings (click her to expand)
System info
Windows 10, build 19045
Steps to reproduce
-race
and run it$ go build -race && ./reproducer
The text was updated successfully, but these errors were encountered: