Repository navigation
Conversation
moetemp
marked this pull request as draft
October 26, 2026 16:53
moetemp
force-pushed
the
moe/stream-service-messages
branch
3 times, most recently
from
October 28, 2026 08:56
482ec01 to
5068d41
Compare
moetemp
added a commit
to moetemp/nexgen
that referenced
this pull request
Oct 28, 2026
The Stream protos are A1's files again, and the runtime proto is K10's, so the sample matches the crate. `CreateStreamResponse` has no `status` now. The descriptor set and the bindings are rebuilt with the README's recipe.
This was referenced Oct 28, 2026
moetemp
added a commit
to moetemp/nexgen
that referenced
this pull request
Oct 29, 2026
The Stream protos are A1's files again, so the sample matches the crate. `CreateStreamResponse` has no `status` now. The descriptor set and the bindings are rebuilt with the README's recipe.
moetemp
force-pushed
the
moe/stream-service-messages
branch
from
October 29, 2026 04:06
5068d41 to
44519d8
Compare
tconley1428
pushed a commit
to temporalio/nexgen
that referenced
this pull request
Oct 29, 2026
The sample takes the part of Brook's WIT that nexgen generates, on the Stream protos of temporalio/api#895 at 44519d8a. No SDK has those protos, so the sample projects hold their bindings. The sample is a System Nexus service, so its .NET output builds in its own project. Only .NET generates the service, since Python and TypeScript panic on the read item's oneof.
moetemp
added a commit
to temporalio/nexgen
that referenced
this pull request
Oct 31, 2026
…io (#311) ### What changed? This PR moves the stream sample's Python bindings of the Stream protos into a local package, `temporalio_stream_protos/`, that installs them into `temporalio`. Only the sample changes. nexgen and the generated code stay as they are. - The package adds only the Stream modules under `temporalio/api/`. The sample depends on it through a `uv` `path` source, and `streamprotos/` goes away. - basedpyright now checks `wit/stream_service`. ### Why? The Stream protos of `temporalio/api#895` aren't in a released `temporalio` yet. The generated code already imports them from `temporalio.api`, where a release will have them. When it does, the package goes away. ### How did you test it? Link to a test plan if any - - [x] Unit Tests - [ ] Staging - [ ] End to End Tests `test_stream_service.py` round-trips each read item kind through the `temporalio.api` classes.
moetemp
added a commit
to moetemp/nexgen
that referenced
this pull request
Oct 31, 2026
The stream sample's WIT is the Stream service WIT of the protos PR, with the sample's own definition, and its protos and bindings are those of the PR. The sample gains the `withdraw_run` helper that the WIT's sources call.
moetemp
added a commit
to moetemp/nexgen
that referenced
this pull request
Nov 3, 2026
The stream sample's WIT is the Stream service WIT of the protos PR, with the sample's own definition, and its protos and bindings are those of the PR. The sample gains the `withdraw_run` helper that the WIT's sources call.
moetemp
added a commit
to temporalio/nexgen
that referenced
this pull request
Nov 3, 2026
1 of 3 tasks
tconley1428
pushed a commit
to temporalio/nexgen
that referenced
this pull request
Nov 4, 2026
moetemp
added a commit
to temporalio/sdk-rust
that referenced
this pull request
Nov 5, 2026
A create fails with ALREADY_EXISTS unless it uses an existing Stream, and a request id keeps a retried create from failing as a conflict. The protos match temporalio/api#895 again.
This was referenced Nov 5, 2026
moetemp
added a commit
to temporalio/nexgen
that referenced
this pull request
Nov 5, 2026
The stream sample's WIT is the Stream service WIT of the protos PR. A directive that nexgen doesn't support yet stays a TODO comment, and the `body-t` alias stays `payload` until nexgen supports its type parameter. The protos and bindings are those of the PR. The sample gains the `request_id` helper that the create's source calls. It loses the owner helper, since a create no longer sends an owner.
This was referenced Nov 5, 2026
Closed
The append and the close name the Producer directly, so StreamWriter is gone. Each read item carries its own offset. The WIT drops the options of the fields that the API requires, so callers can't leave them out.
The close offset says only where the Stream ended. The namespace comments say that the SDK sets it and that only the server reads it.
That head has the sample synced to this WIT. Its nexgen code is the same as at the earlier pin.
A higher epoch fences the lower one, and a reader may hide its Records, for a client too. A client with no name of its own is a new Producer in each process.
An SDK writer is an object now, so no call names a writer by id. A closed writer fails as CLOSED. A Record needs a body, and a timestamp needs both of its fields.
The two comments held for one kind of Store each.
A read gives only Records, tells of a close with done, and starts after an offset. A client has no epoch, and a describe gives no Retention, which is a backend setting. The fields that only the server reads come back with the design of Workflow reads on native Streams.
False and not set mean the same for this flag, so an option gave the SDK a third state with no meaning.
That revision makes a list<u8> parameter of a resource method the bytes of its proto field, which the read's from-offset needs.
A caller can pass its own Producer, and the default helper picks one by where the code runs. An append gives back its response, so the API can grow without a breaking change.
The SDKs and the docs say Store for the thing that holds a Stream, so the ref's field says it too.
The resource's `append` takes an optional `sequence`, so a caller that numbers its batches gets each one written once. Two comments no longer name an SDK writer.
Two offsets of one Stream compare bytewise, so the server can order them too. On a Store, Workflow code writes through a Local Activity, so the Workflow Producer comments no longer describe a close there.
Workflow code has no built-in append, close or read in this release, so the Workflow target omits the three methods and the client target keeps them. The two `producer` parameters take their value from `@nexus.default`. The nexgen pin moves to `main`, which has both rules.
Workflow code appends through a Local Activity and closes through an Activity, so the Workflow target has both methods again. It still omits read.
The next commit adds three methods to the Stream WIT that use the directive, and no commit of nexgen `main` has it yet.
Client, Activity and Workflow code read a Stream with these three methods. The SDK implements each one, so no operation binds them, and the Workflow Stream still has no page read.
The SDK's check runs when code takes a method of a Stream, so a call that nothing awaits fails too.
The WIT of `iter` needs `sync=true` on `@nexus.helper`, and `@nexus.support-type`.
Workflow code reads a Stream with `iter`, which gives each Record as it arrives. The three scan methods and their types are out, to keep the API small.
Workflow code on a Store can write in its Workflow Task, so the comment no longer says that it always writes through a Local Activity.
The guard was there for the functions of take, filter and reduce, which the WIT no longer has.
The fork now has `@nexus.helper`, its `sync` form and `@nexus.support-type` in one pull request, so the commit of the earlier pin is no longer on a branch of an open one.
The review asked for one read API on both targets. So the separate Workflow read and its support type are gone, and the nexgen pin has the poll iterators of the Workflow target.
The Store option is `producer_idle_ttl` since the review of the Redis options.
Workflow appends go through Core inside the Workflow Task.
moetemp
force-pushed
the
moe/stream-service-messages
branch
from
November 19, 2026 04:08
194c2c9 to
e4be454
Compare
moetemp
marked this pull request as ready for review
November 19, 2026 04:12
The poll iterators of the Workflow target are on nexgen's main now, so the fork isn't needed. The generated WIT doesn't change.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed?
This PR adds the Stream service messages and the Stream service WIT, marked experimental.
Producerand epoch, so a newer attempt fences an older one. A read gives the Records in order and tells of a close withdone, and an offset is opaque, orderedbytes.CreateStreamfails when the Stream exists, unlessid_conflict_policyisUSE_EXISTING. A retry with the samerequest_idgets the Stream it made.readand its poll iterator.main, until a release has the directives they use. There's noservice.protoyet.Why?
The SDKs and the Redis Store already use these messages, so they need one home before a server serves them. temporalio/sdk-rust#1733 has a copy of these files only to build, so this PR is the place to review the messages.
Breaking changes
None. These are new files.
Server PR
None needed for now.