Skip to content

Pinned Core at the external runtime's channel wake. - #41

Open
moedash wants to merge 1 commit into
moe/AI-198-if-pyext-4-constructor-publishfrom
moe/AI-198-if-pyext-5-core-wake-pin
Open

moedash wants to merge 1 commit into
moe/AI-198-if-pyext-4-constructor-publishfrom
moe/AI-198-if-pyext-5-core-wake-pin

Conversation

@moedash

@moedash moedash commented Oct 3, 2026

Copy link
Copy Markdown
Owner

This PR pins the external-streams Core that wakes parked stream readers through notification channels.

What changed?

  • temporalio/bridge/sdk-core points at the channel-wake Core, and .gitmodules names its branch.
  • poe gen-protos adds the WorkflowStreamChannels workflow command to the bridge protos. That's the only generated change, and the pin forces it.

Part of AI-198 (epic AI-37).

Why?

The next PR makes the external runtime report which channels its open readers listen on. Core needs this version to take that report and keep the server's subscriptions in step with it. It's also the Core that resumes a parked external wait when a channel notification arrives. Keeping the pin separate means the wake PR shows only Python.

How did you test it?

Link to a test plan if any -

  • Unit Tests
  • Staging
  • End to End Tests

The bridge builds and poe lint is clean. The external stream suite, the worker workflow suite and the visitor tests pass on the dev server. The channel cases pass with -E against a channel server. Nothing emits the new command yet.

This Core resumes parked external waits from channel notifications and keeps
the server's subscriptions in step with the channels lang reports, so the
bridge protos gain the WorkflowStreamChannels command.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

skip-changelog Changelog entry rides another PR

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant