Repository navigation
Conversation
This was referenced Oct 28, 2026
yohamta0
force-pushed
the
stack/31-x1
branch
2 times, most recently
from
October 29, 2026 10:50
bfc860e to
81450af
Compare
yohamta0
force-pushed
the
stack/30-e3
branch
2 times, most recently
from
October 29, 2026 12:58
7ec6acd to
79732f4
Compare
yohamta0
force-pushed
the
stack/31-x1
branch
2 times, most recently
from
October 30, 2026 06:44
b885b1b to
e764307
Compare
yohamta0
force-pushed
the
stack/30-e3
branch
2 times, most recently
from
October 30, 2026 08:07
838cbd8 to
dc7227f
Compare
yohamta0
force-pushed
the
stack/31-x1
branch
2 times, most recently
from
October 30, 2026 08:43
299833a to
734925d
Compare
yohamta0
force-pushed
the
stack/31-x1
branch
2 times, most recently
from
October 31, 2026 05:37
0619863 to
e0238cf
Compare
* e2e: workspace specs (2/2) * Drop dead e2e absence checks, assert step clear * Expect a disabled run caret for executing roles * Check profile scope and tab names in e2e
The build workflows used /var/lib/dagu/demo-build as working_dir, so they failed outside the container image. A relative working_dir resolves against the DAG file, so ../demo-build follows any data directory that setup.sh fills. The router and the repeat demos drew numbers from RANDOM, which dash does not set, so the router always took the 2xx branch. The repeat condition was also a value match, where backtick text is literal, so it never matched and always ran six times. Both now read a random byte from /dev/urandom, and the repeat uses a command-check condition. The chain-backup comment now says that both schedules run the whole chain, and the README says that the demo runs on a schedule and that setup.sh overwrites earlier copies.
The merge, load, middle and use steps echoed outputs of earlier steps
inside double quotes. The reference expands to JSON with its own double
quotes, which the shell then removed, so the demo printed
orders={orders:42} instead of the JSON it read. The steps now print
through a quoted heredoc, where the shell leaves the text alone.
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.
All PRs of the stack
Summary
This PR adds
examples/workspace-demo/: nine workflows and a setup script. They show the graph, a router, reuse of earlier outputs, chains, repeating steps and two build workflows.Why
The workspace needs sample workflows to try it, and to take screenshots. This PR comes last in the stack (after PR 30) and changes no code.
Changes
examples/workspace-demo/dags/graph-etl.yaml,graph-router.yaml: graph workflows with outputs and a router.reuse-costly.yaml: a slow first step, a middle step and a last step. Run it, editmiddle, then run the last step to reuse the outputs.always-running.yaml,repeat-until.yaml: repeating steps.always-runningrepeats every ten seconds with no limit.chain-backup.yaml,chain-report.yaml: chained workflows, one with two schedules.build-site.yaml,build-docs.yaml: build workflows.examples/workspace-demo/demo-build/: input files for the build workflows (index.md,guide.md,style.css, and emptydocs/andout/).examples/workspace-demo/setup.sh: copies the workflows anddemo-buildinto a data directory.examples/workspace-demo/README.md: usage.How to review
README.mdandsetup.sh.reuse-costly.yamlandalways-running.yaml.Pay most attention to these places:
<data-dir>/demo-buildand the work directory/var/lib/dagu/demo-build. Check that the paths are right for the container image.setup.shusesset -euand fails when no argument is given.Tests
No tests are added. Run
./setup.sh <data-dir>, start Dagu withDAGU_HOME=<data-dir>, and run each workflow.Screenshots
No visible UI change in this PR.
The workflows fill the screens of PR 5 to PR 27 with data.