up

up

up

Is this RE https://github.com/dagster-io/dagster/issues/2093?

rebase again

rebase

rebase

Fix pylint

up

Remove extra fields from mocked value

Correctly add pytest-mock

Add mock to dagster-graphql setup.py

Move print out of execute_query_against_remote

• Add checks
• Add test

After working more with partitions, I think introducing this would encourage implementing partitioned-based schedules using the anti-pattern @max mentioned. We can hold off on it until we see a clear need for a partition resource.

Yup, working on a stack that's based on this. Will also add to the changelog

rebase

Up

up

Fix merge conflict

This shouldn't break existing running schedules because the scheduler manages those all by name, correct?

Add comment about why we need to do scheduler_handle.up

Rebase again

Rebase on master

rebase on master

Fix AppCache dataIdFromObject for RunningSchedule

Up

pylint

Up

Up

Up

Up

Move to .utils instead of making a new context.py file

Replace SynchronousExecutionManager with SubprocessExecutionManager in define_subprocess_context_for_file

Requesting review for tests

Add tests

@prha what do you think is the proper way to test this?

ty!

Abandoning for https://dagster.phacility.com/D1853

Actually isort

isort

remove trailing space

rebase

I think it might be best to leave it for type documentation purposes, even though it's being checked right after again.

Remove TODO

Remove extra files

up

Remove cereal files

up

Try CHANGES.md fix again

Rebase on CHANGES.md fix

It seems like the wal changes removs the need for this.

make black (always forget to do this after a codemod)

Rebase

Remove _START constant

Add breaking change to CHANGES.md

up

Up