dagster-io/dagster 1.1.6

# 1.1.6 (core) / 0.17.6 (libraries)

on GitHub

New

• [dagit] Throughout Dagit, when the default repository name __repository__ is used for a repo, only the code location name will be shown. This change also applies to URL paths.
• [dagster-dbt] When attempting to generate software-defined assets from a dbt Cloud job, an error is now raised if none are created.
• [dagster-dbt] Software-defined assets can now be generated for dbt Cloud jobs that execute multiple commands.

Bugfixes

• Fixed a bug that caused load_asset_value to error with the default IO manager when a partition_key argument was provided.
• Previously, trying to access context.partition_key or context.asset_partition_key_for_output when invoking an asset directly (e.g. in a unit test) would result in an error. This has been fixed.
• Failure hooks now receive the original exception instead of RetryRequested when using a retry policy.
• The LocationStateChange GraphQL subscription has been fixed (thanks @****roeij !)**
• Fixed a bug where a sqlite3.ProgrammingError error was raised when creating an ephemeral DagsterInstance, most commonly when build_resources was called without passing in an instance parameter.
• [dagstermill] Jupyter notebooks now correctly render in Dagit on Windows machines.
• [dagster-duckdb-pyspark] New duckdb_pyspark_io_manager helper to automatically create a DuckDB I/O manager that can store and load PySpark DataFrames.
• [dagster-mysql] Fixed a bug where versions of mysql < 8.0.31 would raise an error on some run queries.
• [dagster-postgres] connection url param “options“ are no longer overwritten in dagit.
• [dagit] Dagit now allows backfills to be launched for asset jobs that have partitions and required config.
• [dagit] Dagit no longer renders the "Job in repo@location" label incorrectly in Chrome v109.
• [dagit] Dagit's run list now shows improved labels on asset group runs of more than three assets
• [dagit] Dagit's run gantt chart now renders per-step resource initialization markers correctly.
• [dagit] In op and asset descriptions in Dagit, rendered markdown no longer includes extraneous escape slashes.
• Assorted typos and omissions fixed in the docs — thanks @C0DK and @akan72!

Experimental

• As an optional replacement of the workspace/repository concepts, a new Definitions entrypoint for tools and the UI has been added. A single Definitions object per code location may be instantiated, and accepts typed, named arguments, rather than the heterogenous list of definitions returned from an @repository-decorated function. To learn more about this feature, and provide feedback, please refer to the Github Discussion.
• [dagster-slack] A new make_slack_on_freshness_policy_status_change_sensor allows you to create a sensor to alert you when an asset is out of date with respect to its freshness policy (and when it’s back on time!)

Documentation

• Refreshed dagstermill guide and reference page https://docs.dagster.io/integrations/dagstermill
• New declarative scheduling guide: https://docs.dagster.io/guides/dagster/scheduling-assets
• New dagster-snowflake guide: https://docs.dagster.io/integrations/snowflake
• Added docs for asset code versioning: https://docs.dagster.io/concepts/assets/software-defined-assets#asset-code-versions
• Added docs for observable source assets: https://docs.dagster.io/concepts/assets/asset-observations#observable-source-assets