Add out_of_order_signals scenario#369
Merged
Merged
Conversation
Each workflow expects N signals (event_1..event_N) processed strictly in sequence; signals are sent in a deterministically shuffled order for a configurable fraction of workflows. Stresses signal queuing, workflow buffering across arrivals, and forward progress when an early-expected event arrives late. stack-info: PR: #369, branch: lilydoar/stack/3
lilydoar
added a commit
that referenced
this pull request
May 28, 2026
Each workflow expects N signals (event_1..event_N) processed strictly in sequence; signals are sent in a deterministically shuffled order for a configurable fraction of workflows. Stresses signal queuing, workflow buffering across arrivals, and forward progress when an early-expected event arrives late. stack-info: PR: #369, branch: lilydoar/stack/3
lilydoar
force-pushed
the
lilydoar/stack/3
branch
from
758b821 to
9ab0056
Compare
lilydoar
force-pushed
the
lilydoar/stack/2
branch
from
f38c2d9 to
8ab0c23
Compare
This was referenced May 28, 2026
lilydoar
added a commit
that referenced
this pull request
Jun 1, 2026
Each workflow expects N signals (event_1..event_N) processed strictly in sequence; signals are sent in a deterministically shuffled order for a configurable fraction of workflows. Stresses signal queuing, workflow buffering across arrivals, and forward progress when an early-expected event arrives late. stack-info: PR: #369, branch: lilydoar/stack/3
lilydoar
force-pushed
the
lilydoar/stack/3
branch
from
9ab0056 to
9a11988
Compare
lilydoar
added a commit
that referenced
this pull request
Jun 1, 2026
Each workflow expects N signals (event_1..event_N) processed strictly in sequence; signals are sent in a deterministically shuffled order for a configurable fraction of workflows. Stresses signal queuing, workflow buffering across arrivals, and forward progress when an early-expected event arrives late. stack-info: PR: #369, branch: lilydoar/stack/3
lilydoar
force-pushed
the
lilydoar/stack/3
branch
from
9a11988 to
f0b1a25
Compare
lilydoar
added a commit
that referenced
this pull request
Jun 2, 2026
Each workflow expects N signals (event_1..event_N) processed strictly in sequence; signals are sent in a deterministically shuffled order for a configurable fraction of workflows. Stresses signal queuing, workflow buffering across arrivals, and forward progress when an early-expected event arrives late. stack-info: PR: #369, branch: lilydoar/stack/3
lilydoar
force-pushed
the
lilydoar/stack/3
branch
from
f0b1a25 to
0925049
Compare
lilydoar
added a commit
that referenced
this pull request
Jun 2, 2026
Each workflow expects N signals (event_1..event_N) processed strictly in sequence; signals are sent in a deterministically shuffled order for a configurable fraction of workflows. Stresses signal queuing, workflow buffering across arrivals, and forward progress when an early-expected event arrives late. stack-info: PR: #369, branch: lilydoar/stack/3
lilydoar
force-pushed
the
lilydoar/stack/3
branch
from
0925049 to
b910316
Compare
THardy98
reviewed
Jun 3, 2026
| if err != nil { | ||
| return err | ||
| } | ||
| rng := oooSeededRng(run.RunID, run.Iteration) |
Contributor
There was a problem hiding this comment.
Might be worth at some point creating a utils file/package with helpers like these seeded rng functions.
Not blocking
THardy98
approved these changes
Jun 3, 2026
lilydoar
force-pushed
the
lilydoar/stack/2
branch
from
40b3e48 to
7ae5d9d
Compare
lilydoar
added a commit
that referenced
this pull request
Jun 3, 2026
Each workflow expects N signals (event_1..event_N) processed strictly in sequence; signals are sent in a deterministically shuffled order for a configurable fraction of workflows. Stresses signal queuing, workflow buffering across arrivals, and forward progress when an early-expected event arrives late. stack-info: PR: #369, branch: lilydoar/stack/3
lilydoar
force-pushed
the
lilydoar/stack/3
branch
from
b910316 to
f810bdb
Compare
lilydoar
force-pushed
the
lilydoar/stack/3
branch
from
f810bdb to
2e44bd2
Compare
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.
Stacked PRs:
Add out_of_order_signals scenario
Each workflow expects N signals (event_1..event_N) processed strictly in
sequence; signals are sent in a deterministically shuffled order for a
configurable fraction of workflows. Stresses signal queuing, workflow
buffering across arrivals, and forward progress when an early-expected
event arrives late.