canary

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

god damn yaml templates

rebase

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:

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?

this seems fine, double check if you need to add the check stuff

special case singurlar input_def

rebaesw

rm print()

update serdes and seven to better handle py2

nice - just make sure to cleanup unused stuff

rebase + comment

it seems like something bad is happening in changed.md thats causing the autoformatter to go nuts

okay

lint

rebase

black

use correct fixture

use conn_string to get DB fixture

defer to @schrockn since I think i missed the last part of the convo on determining the best approach

rm debug

py2

nice

shims maybe? builtins on its own just doesn't mean much

let @prha take this one

rebase

sadface

up

test plan
BK

fix

is Nullable going to newish python only users up since there is no notion of null ? I think Noneable is worth discussing. Going to leave this one open for more debate

im down - I'll go ahead and accept but probably worth double checking with @max if you want more thoughts

Update [1] then good to go I think

gogogo

for the error messages I agree that we can tolerate losing the bit of context since the stack trace should point you in the right direction - but I think we can do better than whats in the diff as it stands

What do you think about having two contexts: ScheduleExecutionContext to pass to the schedule methods, and PartitionSelectionContext for the partition selector?
Ideally, we could just pass the DagsterGraphQLContext around