refactor(client): migrate clients to http-client (rm tide 4/5)#4706
refactor(client): migrate clients to http-client (rm tide 4/5)#4706sveitser wants to merge 10 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. |
1fafce3 to
7e9a4f7
Compare
Leaf and consensus clients, catchup StatePeers, the light-client query-service provider, orchestrator client, builder event wrapper, prover relay clients, node bins, and the test suites move to http_client::Client. espresso-api drops its temporary local AppHealth/HealthStatus for the http-client definitions. The unused surf-disco workspace dependency is removed; servers keep tide-disco until the next PR. Wire compat with released tide servers (binary-upgrade CI): vbs body_binary double-encoding and binary-default Accept headers are preserved by http-client.
7e9a4f7 to
7c9ac8a
Compare
1 participant
catchup StatePeers, light-client provider, orchestrator client,
builder event wrapper, prover, bins, tests
Review focus: binary-upgrade CI new-from-old scenarios (new client
vs released tide servers); Accept-header defaults; healthcheck type
move.