Channels
dagster-de
topic-async-execution
dagster-jp
dagster-cube
gigs-freelance
dagster-wandb
dagster-feedback
dagster-machine-learning
dagster-bigquery
dagster-support
dagster-dask
dagster-snowflake
dagster-releases
dagster-dbt
faq-read-me-before-posting
tools
dagster-pipes
project-flexible-range-backfills
data-platform-design
events
dagster-serverless
dagster-noteable
introductions
dagster-airflow
dagster-cloud
random
dagster-airbyte
dagster-spatial
announcements
github-discussions
豆瓣酱帮
dagstereo
dagster-ecs
dagster-kubernetes
jobs
dagster-showcase
data-quality-asset-checks
Powered by
#announcements
Title
n
Noah K
10/28/2020, 8:30 PM
Unrelated question to the above: is there a reason SyncInMemoryLauncher uses a weakref of the instance passed in from initialze instead of the instance passed to launch_run?
https://github.com/dagster-io/dagster/blob/1aa474e04ccd91b089cffe4a597799dab4de5c3a/python_modules/dagster/dagster/core/launcher/sync_in_memory_run_launcher.py#L46
Post