Repository navigation
Add bounded workflow observations for operator clients - #103
Merged
Merged
Conversation
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
2 participants
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.
Change
Adds
Client::workflowObservation()for Waterline's bounded initial run view.The namespace-scoped operator route returns current waits, independently observed
related run statuses, recent failure references and a bounded history page.
Application values and external payload references remain encoded.
Search attribute context requires an explicit list of at most 20 distinct keys.
History uses an opaque run-scoped cursor with the original sequence ceiling.
Invalid selections are rejected before transport. An unsupported Server's
refusal is preserved without a full diagnostics fallback.
Prepares PHP SDK 2.2.3. Control-plane and worker protocol versions remain the
same. Server implementation: durable-workflow/server#307.
Owning outcome: durable-workflow/waterline#141.
Verification
Focused transport, namespace, context, opaque history and refusal checks are
included. Normal repository checks must pass before merging. Registry publication
and a fresh published consumer follow the merged-source checks.
Consumer follow-through
Waterline will select the published SDK and Server before its service view and
five fixture qualification. The website receives one coherent tuple update after
the Waterline release. Python, Rust and CLI worker behavior is unchanged.