-
Notifications
You must be signed in to change notification settings - Fork 18
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
"Session handle still has owners" #32
Comments
The issue is with how the |
It looks like v4 of |
I'm also working on a new direction which addresses this among other things. Please see #56. |
I've released v0.1.0 of tower-sessions for folks who would like to try that. This new crate does not use async-session and takes an approach to managing inner state that's inline with other tower middleware, like tower-cookies. If you end up trying it, please let me know how it goes. |
I was trying to use axum-sessions within the leptos framework and I encountered an error where leptos seemed like it would not drop AuthContext. I reported it to leptos and it seems like it is an issue with your middleware:
axum-sessions/src/session.rs
Lines 346 to 348 in 4c7480a
Why does this type implement
Clone
and then panic if it is cloned and used? Why is this not documented? Surely this edge case can be worked around, or at least pushed to a compile-time error?If you would like to see the issue, this project errors with this reproducibly here
The text was updated successfully, but these errors were encountered: