ls command.execution: celery-k8s:
GCSComputeLogManager using a string or environment variable instead of passing a path to a credentials file. Thanks @silentsokolov!dagster instance migrate would run out of memory when migrating over long run histories.dagster_aws.s3.sensor.get_s3_keys that would return no keys if an invalid s3 key was providedmy_log.info("foo %s", "bar") would cause errors in some scenarios.build_assets_job. The asset graph shows each node in the job’s graph with metadata about the asset it corresponds to - including asset materializations. It also contains links to upstream jobs that produce assets consumed by the job, as well as downstream jobs that consume assets produced by the job.load_assets_from_dbt_project and load_assets_from_dbt_project that would cause runs to fail if no runtime_metadata_fn argument were supplied.@asset not to infer the type of inputs and outputs from type annotations of the decorated function.@asset now accepts a compute_kind argument. You can supply values like “spark”, “pandas”, or “dbt”, and see them represented as a badge on the asset in the Dagit asset graph.Changed VersionStrategy.get_solid_version and VersionStrategy.get_resource_version to take in a SolidVersionContext and ResourceVersionContext, respectively. This gives VersionStrategy access to the config (in addition to the definition object) when determining the code version for memoization. (Thanks @RBrossard!).
Note: This is a breaking change for anyone using the experimental VersionStrategy API. Instead of directly being passed solid_def and resource_def, you should access them off of the context object using context.solid_def and context.resource_def respectively.