dagster-slack 0.13.18

on Python PyPI

New

• Op selection now supports selecting ops inside subgraphs. For example, to select an op my_op inside a subgraph my_graph, you can now specify the query as "my_graph.my_op".
• The error message raised on failed Dagster type check on an output now includes the description provided on the TypeCheck object.
• The dagster asset wipe CLI command now takes a --noprompt option.
• Added the new Map config type, used to represent mappings between arbitrary scalar keys and typed values. For more information, see the Map ConfigType docs.
• build_resources has been added to the top level API. It provides a way to initialize resources outside of execution. This provides a way to use resources within the body of a sensor or schedule: #3794
• The dagster-daemon process now creates fewer log entries when no actions are taken (for example, if the run queue is empty)
• [dagster-k8s] When upgrading the Dagster helm chart, the old dagster-daemon pod will now spin down completely before the new dagster-daemon pod is started.
• [dagster-k8s] A flag can now be set in the Dagster helm chart to control whether the Kubernetes Jobs and Pods created by the K8sRunLauncher should fail if the Dagster run fails. To enable this flag, set the ``failPodOnRunFailure` key to true in the run launcher portion of the Helm chart.
• [dagster-dbt] Fixed compatibility issues with dbt 1.0. The schema and data arguments on the DbtCliResource.test function no longer need to be set to False to avoid errors, and the dbt output will be no longer be displayed in json format in the event logs.
• Dagster Types can now have metadata entries attached to them.
• DagsterGraphQLClient now supports submitting runs with op/solid sub-selections.
• [dagit] The Asset Catalog view will now include information from both AssetMaterializations and AssetObservation events for each asset.
• [dagit] [software-defined-assets] A warning will now be displayed if you attempt to backfill partitions of an asset whose upstream dependencies are missing.

Bugfixes

• When Dagit fails to load a list of ops, the error message used the legacy term “solids”. Now it uses “ops”.
• Runs created using dagster versions 0.13.15 / 0.13.16 / 0.13.17 might display an incorrect timestamp for its start time on the Runs page. This would only happen if you had run a schema migration (using one of those versions) with the dagster instance migrate CLI command. Running the dagster instance reindex command should run a data migration that resolves this issue.
• When attempting to invoke run status sensors or run failure sensors, it will now incur an error. Run status/failure sensor invocation is not yet supported.
• [dagster-k8s] Fixed a bug in the sanitization of K8s label values with uppercase characters and underscores

Community Contributions

• [software-defined-assets] Language in dagit has been updated from “refreshing” to “rematerializing” assets (thanks @Sync271!)
• [docs] The changelog page is now mobile friendly (thanks @keyz!)
• [docs] The loading shimmer for text on docs pages now has correct padding (also @keyz!)

Experimental

• [software-defined-assets] The namespace argument of the @asset decorator now accepts a list of strings in addition to a single string.
• [memoization] Added a missing space to the error thrown when trying to use memoization without a persistent Dagster instance.
• [metadata] Two new metadata types, TableSchemaMetadataEntryData and TableMetadataEntryData allow you to emit metadata representing the schema / contents of a table, to be displayed in Dagit.