Mar 18 2021
yeah these should eventually go under test
Failing test is not related
would be worth showing the backfill uis here too
Mar 17 2021
Mar 16 2021
+1 for the literal include code snippets. sorry for the extra work here. the previous schedule code snippets weren't under test so we converted all untested literal include code snippets into inline snippets to make it explicit. happy to do that for you if needed.
Mar 15 2021
Pin sqlalchemy in dagster-airflow
It looks like flask_admin in airflow has a broken import caused by sqlalchemy==1.4.0 as well, but the problem here is that db.engine.Result is only available in 1.4.0, and ResultProxy isn't. So if we pin to <1.4.0 in only dagster-airflow, then dagster-postgres won't work
@sidkmenon could I get another look at the ResultProxy change?
Let me know if my suggestion doesn't makes or doesn't result in the desired behavior you're trying to achieve here. Not 100% familiar with the docker run launcher.
In some cases, users want their entrypoint to _not_ be dagster, because they could be using something like conda. This is because dagster isn't an available command in their virtual environment. Here's an example of where a similar problem came up in dagster-k8s: https://github.com/dagster-io/dagster/issues/3081.
Thank you! This is great!
Mar 14 2021
Mar 13 2021
Thanks for the fix and tests!
Mar 12 2021
so sick, can you put a quick readme of how to get this up and running locally?