Skip to content

refactor: drop tide-disco from node, orchestrator, lcqs (rm tide 5/5)#4707

Draft
sveitser wants to merge 13 commits into
ma/http-client-migrationfrom
ma/drop-tide-disco
Draft

refactor: drop tide-disco from node, orchestrator, lcqs (rm tide 5/5)#4707
sveitser wants to merge 13 commits into
ma/http-client-migrationfrom
ma/drop-tide-disco

Conversation

@sveitser

Copy link
Copy Markdown
Collaborator
  • deletes the tide App construction and the endpoints tree
  • swaps tide-disco re-exported types to disco-types originals
  • status metrics() reimplemented with prometheus::TextEncoder
    (byte-identical exposition); moves get_public_env_vars
  • pure deletion plus mechanical swaps; no behavior change
  • tide-disco remains in hotshot-builder, hotshot/testing,
    builder-api, events-service, hqs internals; separate effort

@gemini-code-assist

Copy link
Copy Markdown
Contributor
Using Gemini Code Assist

The 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 /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

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 .gemini/ folder in the base of the repository. Detailed instructions can be found here.

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.

@sveitser
sveitser force-pushed the ma/http-client-migration branch from 1fafce3 to 7e9a4f7 Compare July 17, 2026 00:21
@sveitser
sveitser force-pushed the ma/drop-tide-disco branch from 66a6119 to 36c2885 Compare July 17, 2026 00:21
The axum server serves everything; the tide-disco App was built and
immediately dropped in every serve mode purely to keep the module
definitions compiling. Delete the App construction and the endpoints
tree, swap tide-disco re-exported types (StatusCode, Error, ServerError)
to their disco-types originals, move get_public_env_vars, and
reimplement status metrics() with prometheus::TextEncoder
(byte-identical exposition). tide-disco remains only in the hotshot
builder/testing crates and the query/events service definitions.
@sveitser
sveitser force-pushed the ma/drop-tide-disco branch from 36c2885 to c172061 Compare July 17, 2026 00:51
@sveitser
sveitser force-pushed the ma/http-client-migration branch from 7e9a4f7 to 7c9ac8a Compare July 17, 2026 00:51
sveitser added 12 commits July 17, 2026 14:53
aide only derives path parameters from named-struct Path<T>
extractors; the v1 handlers all use primitives and tuples, so every
operation showed zero parameters and Swagger's try-it-out could not
fill the URL templates. Declare a required string parameter for every
{name} template segment after finish_api (string because primitive
extractors carry no type metadata; handlers parse).

Also: Swagger UI opens operations with try-it-out enabled; the
test_api example moves to port 5001 (macOS AirPlay holds 5000) and
its startup log lists the v1 doc URLs.
drive_ws_stream only noticed a dead client on the next send, so a
socket whose stream was quiet held its max_connections slot and its
stream task forever; reconnect churn exhausted the demo's budget of 25
and every plain request got 429, killing the native-demo e2e tests
(claim-rewards-loop exits on non-404 and tears the demo down). Poll
the client side with select so disconnects release the slot and end
the task immediately. Regression test now uses a never-yielding
stream.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant