Skip to content

[Bridge] Registered the stream notifier RPCs as System Nexus operations. - #60

Draft
moetemp wants to merge 5 commits into
moe/bridge/v2/n7-callback-progressfrom
moe/bridge/v2/n9-notifier-system-nexus
Draft

moetemp wants to merge 5 commits into
moe/bridge/v2/n7-callback-progressfrom
moe/bridge/v2/n9-notifier-system-nexus

Conversation

@moetemp

@moetemp moetemp commented Oct 14, 2026

Copy link
Copy Markdown
Owner

What changed?

This PR exposes the stream notifier's writes as __temporal_system System Nexus operations.

  • streamnotifier.SystemNexusHandler reuses the frontend's checks and fills the namespace from the Workflow. It calls the notifier in process.
  • The Workflow side refuses a stream reference without its first run, since it routes by business ID before the frontend check.
  • TestStreamNotifierClosedFromWorkflow comes back.

It replaces the Bridge half of moetemp/temporal#42. Forwarding, the xdc test and the owner check tests went to Jetty js4 (moetemp/temporal#52). moetemp/temporal#41 and #48 moved to Jetty whole and have no Bridge v2 layer.

Why?

System Nexus lets the generated bindings call the notifier (DD-79).

How did you test it?

Link to a test plan if any -

  • Unit Tests
  • Staging
  • End to End Tests

nexus_service_test.go and functional TestStreamNotifierClosedFromWorkflow.

A Workflow closes a stream it owns durably only through the __temporal_system endpoint. Attach, detach and notify take their namespace from the Workflow and go to the notifier in process. A stream reference without its first run is refused on this path too.
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