It's not obvious from the test that this would still yield what you actually want.

• add exception-handling tests, add comments, extract resource init

rebase

• add check casts to get_object calls

• tests and refactor

add tests, make sure resource stack tears down on failures

couple things.... still trying to figure out the exception handling. I think we weren't tearing down resources properly before, so figuring out what tests we need to write, change, etc.

• pipeline initialization events, but with generators INSTEAD of context managers

fix scoped_pipeline_context reference

add try/finally, remove double defaults

I initially had it so that the resource/builder/context were yielded along with the event stream, but switched it (per @alangenfeld's suggestion) because it makes it way more explicit in the caller what is going on. I do like this better and we're not mixing types so much. It was getting confusing where we're stacking things at different levels and the type I'm trying to extract is different at each level.

rebase

add syncing hack using useState

My vote is to move to 0.7.0_MIGRATION.md, but we should get this in so others can add to it.

Could just be me, but it feels jarring to switch so often between passive voice, 1st person and 2nd person.

yeah, this makes sense to me.

some spelling / grammar nits, but okay!

Some polish feedback:

• add in memory, sqlite storage impl

Need to fix the other RunStorage implementations...

resolve conflicting tag issues

assert empty run tags

update to sync event_storage, run_storage migration scripts

My vote is to keep create_execution_plan taking in RunConfig.

add method docs

update with resource keys available invariant check

update snapshots

update with gcs update

This feels fine to me.... are we moving away from the define_python_dagster_type calls that are featured in D1906?