-
Notifications
You must be signed in to change notification settings - Fork 33
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Oneshot: UB triggered when using Axum #47
Comments
fereidani
changed the title
UB triggered when using Axum
Oneshot: UB triggered when using Axum
Jul 21, 2024
I'm dropping oneshot feature, going to continue it in another package. Its design need to change and it is not compatible with mpmc channel signal design. |
there are already report open for this bug. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I used the
AsyncSender
andAsyncReceiver
channels and this code started panicking when using kanal. I tried it with Flume and Tokio mpsc channels and there's no issue.It happens when a client cancels their HTTP request, causing Axum to cancel the future that calls this:
It appears that somehow the
.send()
is getting cancelled but therx.await
isn't.The text was updated successfully, but these errors were encountered: