Closed RobbieMcKinstry closed 6 months ago
You're correct – I'll need to update this library for axum 0.7, which I'll see if I can get to in the next couple of days. Hopefully things should be simpler with the upgrade, now that the B
ody generic is gone 🤞
Thank you very much. I appreciate your promptness, and your willingness to make the upgrade! 🚀 ❤️ ✨
Apologies for the delay! There was a more awkward element to the upgrade than I'd hoped (implementing Clone
for request extensions), but I've just published 0.8.0 with support for axum 0.7.0 / hyper 1.0!
Hey there! Thank you very much for resolving this issue and cutting a release! Last night, I was able to upgrade my web sever to the new version. 🚀 Thanks again! ✨
Hello!
Have you been able to upgrade an existing Axum app that uses this library to v0.7.0?
When upgrading to Axum 0.7 and using the
Tx
extractor, I get an error:Note that the type
std::sync::Arc<(dyn object_store::ObjectStore + 'static)>
is another extractor, using axum's builtinState<T>
extractor. I get this same issue on different routes with different values ofT
forState<T>
. The issue persists if I reorder the parameters.From what I can tell, I believe this library is no longer compatible with the latest Axum release, v0.7.0. It's only been out for a few days, and there are a ton of breaking changes, so I wouldn't really be surprised if this were the case. However, I could be wrong, and the error could be in my source code. Here's the intel I've gathered that leads me to believe the issue is in
axum-sqlx-tx
:axum-core@0.3
while Axum v0.7.0 is based onaxum-core@0.4
.axum-sqlx-tx
is thatFromRequestParts
is no longer generic over the request body. However, I don't see this extractor using theB
type parameter, and the error message I'm getting seems to imply that only theS: State
parameter is the issue.Thank you for your time and attention to this issue. ❤️