refactor(api): serve remaining services via axum (rm tide 2/5)#4704
refactor(api): serve remaining services via axum (rm tide 2/5)#4704sveitser wants to merge 11 commits into
Conversation
Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize the Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counterproductive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here. |
feb2eb0 to
748a9c9
Compare
41fb01c to
041b34a
Compare
…a axum State-signature relay server, espresso-dev-node, hotshot-state-prover, submit-transactions, and nasty-client bind axum servers with tide-disco-compatible routes, bodies, and healthchecks (bare HealthStatus, accept-negotiated JSON or vbs). Clients stay on surf-disco.
Ports the remaining tide-disco servers. The orchestrator decodes surf-disco's double-vbs-wrapped request bodies; node-metrics scrapes node identity from /v1/status/metrics; the standalone builder's /healthcheck stays decodable as HealthStatus by hotshot task-impls. Clients stay on surf-disco.
748a9c9 to
4a99eeb
Compare
1 participant
node-metrics, lcqs, standalone builder to axum
Review focus: orchestrator body decoding (12-byte envelope strip);
per-service healthcheck bodies.