Data race when sending raw (e.g. log messages) and other messages in the same request/response #10
Labels
bug
Something isn't working
Comments
bep
added a commit
that referenced
this issue
Apr 3, 2024
That takes a config struct from the client. The old way of configuring the server was to pass env vars (which still works), but this was at best very cumbersome. This also fixes a data race when both sending raw (e.g. log messages) and other responses. Closes #10
bep
added a commit
that referenced
this issue
Apr 3, 2024
That takes a config struct from the client. The old way of configuring the server was to pass env vars (which still works), but this was at best very cumbersome. This also fixes a data race when both sending raw (e.g. log messages) and other responses. Closes #10
bep
added a commit
that referenced
this issue
Apr 3, 2024
That takes a config struct from the client. The old way of configuring the server was to pass env vars (which still works), but this was at best very cumbersome. This also fixes a data race when both sending raw (e.g. log messages) and other responses. Closes #10
bep
added a commit
that referenced
this issue
Apr 3, 2024
That takes a config struct from the client. The old way of configuring the server was to pass env vars (which still works), but this was at best very cumbersome. This also fixes a data race when both sending raw (e.g. log messages) and other responses. Closes #10
bep
added a commit
that referenced
this issue
Apr 3, 2024
That takes a config struct from the client. The old way of configuring the server was to pass env vars (which still works), but this was at best very cumbersome. This also fixes a data race when both sending raw (e.g. log messages) and other responses. Closes #10
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
No description provided.
The text was updated successfully, but these errors were encountered: