Open kKdH opened 10 months ago
It looks like most conflicts happen, because the reqwest
library isn't yet ready for using hyper
and http
1.0: https://github.com/seanmonstar/reqwest/issues/2039
Trying to upgrade axum
or hyper
individually, forces those to use a new version of the http
library, incompatible with what reqwest
supports (0.2).
The tonic
library is not yet ready either: https://github.com/hyperium/tonic/issues/1579
reqwest
is now ready for upgrade, but tonic
is still not ready.
A partial upgrade still fails due to two different versions of the http
crate (0.2.12
and 1.1.0
) being pulled in as dependencies.
tonic
is now also ready, as of version 0.12.0: https://github.com/hyperium/tonic/releases/tag/v0.12.0
Upgrade attempted on branch issue-29-hyper-http-upgrade.
OpenTelemetry still seems to not be ready: https://github.com/open-telemetry/opentelemetry-rust/pull/1674
OpenTelemetry is ready, now waiting for tracing-opentelemetry
: https://github.com/tokio-rs/tracing-opentelemetry/issues/154
tracing-opentelemetry
is ready. Struggling with upgrading Axum for our gRPC+HTTP backend. The relevant example has not been updated yet, so might not yet be easily possible: https://github.com/tokio-rs/axum/blob/main/examples/rest-grpc-multiplex/src/main.rs
There is a new version of axum (our web application framework), we would like to update to. The update relates also to hyper, http, and reqwest which should be updated too. Due to several breaking changes the update is more complex.