Repository navigation
Conversation
A Workflow appends to and subscribes to server-held streams with two commands. Workflow Tasks carry the records out of band, and History keeps only the offset ranges. The new values take the numbers after the channel's.
Owner
Author
|
Paused per the 2026-10-05 design review (the decision record is on the proposal page, section 14). Resumes in phase 2 with the CHASM notification work. The branch stays as a pin. |
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
1 participant
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.
This PR adds native server streams to the public API.
What changed?
StreamSlice,StreamRangeandStreamStartPositionjoin the envelope instream/v1.AppendStreamRecordsandSubscribeStreamcommands, each with its own History event. The appended event carries only the offset range.PollWorkflowTaskQueueResponse.stream_slicescarries the records a task consumes.WorkflowTaskCompletedEventAttributes.consumed_stream_rangesrecords which offsets the task consumed.StreamRecord.body's comment now names the two paths where a payload codec reaches a record: the append command and the poll slices.openapi/regenerated.Part of AI-198 (epic AI-37).
Why?
A Workflow that streams records today pushes each one through History, as Signals, Updates or activity results. History then grows with the data, not the work. Here the records live in a log the server keeps next to the Workflow. History only records offsets, so it grows with tasks, and replay reads the same records back by offset.
How did you test it?
Link to a test plan if any -
make buf-lintandmake api-linterare clean, with the inline exemptions for the "from" and "to" offset fields.make http-api-docsregeneratesopenapi/. Themake go-grpcoutput builds and vets in a scratch module. The server, Core and Python PRs in the series run append, subscribe and replay end to end.