8000 Added Repeat component. by rybesh · Pull Request #22 · noflo/noflo · GitHub
[go: up one dir, main page]

Skip to content

Added Repeat component. - #22

Merged
bergie merged 1 commit into
noflo:masterfrom
rybesh:repeat
May 23, 2012
Merged

bergie merged 1 commit into
noflo:masterfrom
rybesh:repeat

Conversation

@rybesh
@rybesh rybesh commented May 22, 2012
Copy link
Copy Markdown
Contributor

Just a simple repeater component. I've needed this to get subgraphs to work properly in some cases.

bergie added a commit that referenced this pull request May 23, 2012
Added Repeat component.
@bergie
bergie merged commit 9941aae into noflo:master May 23, 2012
AsherBond pushed a commit to AsherBond/noflo that referenced this pull request Oct 12, 2026
bergie added a commit that referenced this pull request Oct 19, 2026
…ession pin (work document #48)

Distills the noflo-jekyll document leg (work document #35 updates
#14-#22) to its engine shape and runs it through the actual wrapAssembly
machinery: a gate-model render component — standing bracket-framed
config on a scoped:false control port read non-consumingly, per-message
scoped data on two ports gated on both — wrapped as an assembly adapter
(Fork, field extractors, CollectFields), driven with bracket-framed
scoped message envelopes whose arrival order races the config and
stagger with async jitter inside open activations, then driven to EOT
with the closedown cascade asserted.

The negative result this suite pins: on the current engine (post-#1094
control gates, #1092 drain-based closing, #1099 drain pump), roughly
1300 randomized runs across staggered, burst, bounded-edge, multi-
registration-config, and deep-overlap variants delivered every message
and closed down — the intermittent drop class the testbed documented
did not reproduce. Three randomized variants run in CI; the full matrix
rides the WD48_* env knobs.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants