- No tasks found.
set service account name
I would just look through the other tests in dagster_graphql - python_modules/dagster-graphql/dagster_graphql_tests/graphql/test_run_cancellation.py is probably a relevant example
Yeah you’re right. I was reading but wasn’t sure how to isolate a pipeline run, pipeline, Dagster instance, etc. which I need to do in order to make sure lsof can be inspected. As supposed to mocking, How do we do that in other tests?
god damn yaml templates
- oops lint fix
- added mocking testing abilities dep
Abandoning for https://dagster.phacility.com/D1853
just spitballing ideas one thing we could do is keep the box pinned but to the left but change where the shading starts? What i want visually communicated when these things are waiting on eachother for not-data reasons is:
Ahh @alangenfeld that's a good question—for the serial execution engine displaying the dependency graph isn't quite what we want. Could we make the execution plan to include the order it plans to execute steps? Right now the plan doesn't encode enough information for us to know what the true parallelism / timing will look like (at least I don't think?) We could detect the serial execution engine and show them in a waterfall, but we might get the order wrong I think?
- Use fewer large nested functions in Gaant layout code
from use - if you execute the sleepy toy pipeline with the default config which uses inprocess engine - the four parallel steps happen sequentially which is not communicated in the waterfall timed view at all since we pin no the left alignment. Is this something worth addressing now or in a subsequent diff?
Comment Gaant layout algo