Skip to content

[FROZEN][Bridge] Vendored two generic Nexus callback fields. - #197

Closed
moetemp wants to merge 8 commits into
moe/jetty/kj5-early-task-heartbeatfrom
moe/bridge/kb1-pin
Closed

moetemp wants to merge 8 commits into
moe/jetty/kj5-early-task-heartbeatfrom
moe/bridge/kb1-pin

Conversation

@moetemp

@moetemp moetemp commented Oct 17, 2026 •

Copy link
Copy Markdown
Owner

What changed?

This PR vendors two generic Nexus callback fields from api moe/bridge/v2/dr40-sdk-streams (2d204ff9): Callback.NexusHandler.progress_operation = 5 and OnCompleteRequest.receiver_state = 4. The proto and OpenAPI lines match the api commit byte for byte. Core reads neither field. sdk-streams carries the rest of the Nexus progress API in its own new files. Stacked on #196.

Why?

Both fields are new on upstream messages, so the crate can't carry a second copy. sdk-python's client sets progress_operation on start requests that Core decodes, and prost drops unknown fields. sdk-python's follower reads receiver_state in its OnComplete handler, and its protos come from Core's copy. This is Bridge's sdk-rust pin.

How did you test it?

Link to a test plan if any -

  • Unit Tests
  • Staging
  • End to End Tests

Ran the lib suites and the full integ suite on this branch.

@moetemp moetemp changed the title [Bridge] Vendored two generic Nexus callback fields. [FROZEN][Bridge] Vendored two generic Nexus callback fields. Oct 20, 2026
@moetemp

moetemp commented Oct 22, 2026

Copy link
Copy Markdown
Owner Author

Closed as unused. Jetty and Bridge are frozen, and the Brook v4 stack doesn't build on this PR. The branch stays, so this PR can be reopened.

@moetemp moetemp closed this Oct 22, 2026
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