Bump warp and begin axum migration#9001
Conversation
|
Getting off warp 0.3 will save us a |
Fix the cargo-audit failure caused by: - https://rustsec.org/advisories/RUSTSEC-2026-0049 We can't fix it completely yet because `warp 0.3` is keeping us on an old version of `rustls`. Mac's PR here will fix it: - #9001 Co-Authored-By: Michael Sproul <michael@sigmaprime.io>
chong-he
left a comment
There was a problem hiding this comment.
This PR is quite follow-able to me (although I can't say I understand everything).
From my understanding, http_metrics for both BN and VC will be fully on axum after this, but http_api aren't yet. I did some testing to query the APIs and metrics (including some error cases) and can confirm that the behaviour of this PR and Lighthouse v8.1.3 are the same, which is good.
I think this is in a good shape already (of course I could be missing something). I only have some mainly cosmetics comments
Another `rustls-webpki` audit failure: https://rustsec.org/advisories/RUSTSEC-2026-0104 Bump `rustls-webpki` to the latest (unaffected) version. As with the previous `rustls-webpki` vulns, we add an ignore for our older version required by warp 0.3. This ignore will be resolved by #9001 Co-Authored-By: Mac L <mjladson@pm.me>
|
This pull request has merge conflicts. Could you please resolve them @macladson? 🙏 |
|
Some required checks have failed. Could you please take a look @macladson? 🙏 |
|
This pull request has merge conflicts. Could you please resolve them @macladson? 🙏 |
There was a problem hiding this comment.
These error types are pretty lean now and we could consider consolidating, but I kinda like the distinction
|
Queued — the merge queue status continues in this comment ↓. |
Merge Queue Status
This pull request spent 29 minutes 10 seconds in the queue, including 27 minutes 36 seconds running CI. Required conditions to merge
|
This is an alternative to #8280
Proposed Changes
warpto 0.4. This unifieswarpandaxumonto the samehttp,hyper,h2,rustls, etc versions.axum_utilswhich contain common functions and typesAdditional Info
The
tlsfeature was removed inwarp0.4. This is why we pair the axum migration with the bump. Otherwise we would have to implement our own TLS connectivity. Instead, we can rely onaxum-serverto do it for us.This also includes a
warppatch to removeSyncrequirements fromwarpbody types. This (in combination with thewarpversion bump) allows us to completely do away withwarpdrivefrom the original PR. This means theaxumrequests are forwarded straight throughwarp's Tower service natively without any compatibility layer.I have left the mock execution server on
warpas the migration started becoming more complicated than I was expecting and it can easily be left for a future PR.