7692891fff
Both jobs were launched from the Dagster UI, so the numbers in the new section 5.6 come from the daemon and run launcher path rather than from execute_in_process. The tightly coupled run reports one contributing worker across seven steps; the loosely coupled subprocess run reports four, which is the difference the two patterns are supposed to make visible. Hostnames are redacted, process IDs are not. Also ignores a local .dagster_home, which the README's dagster dev instructions will create for anyone who sets DAGSTER_HOME alongside the repo. Changelog: added
9 lines
97 B
Plaintext
9 lines
97 B
Plaintext
*.egg-info/
|
|
**/__pycache__/
|
|
.venv/
|
|
.pytest_cache/
|
|
.coverage
|
|
|
|
.tmp_dagster_home_*/
|
|
.dagster_home/
|