The nux section of dagster.yaml config has been fixed.
Changes when heartbeats occur in the daemon to avoid crashes in certain conditions.
Fixed an issue where passing a workspace file as an argument into the dagster dev command raised an error
[dagit] Fixes an issue with asset names being truncated by long asset descriptions in the asset catalog, making them impossible to click.
[dagit] The backfill page no longer fails to load if any of the asset backfills had assets that were partitioned at the time of the backfill but are no longer partitioned.
Added a new dagster dev command that can be used to run both Dagit and the Dagster daemon in the same process during local development. See the new Running Dagster Locally guide in the docs for more information.
Added instructions for installing the dagster package on M1 and M2 Macs that avoids installation errors when building the grpcio package. See the Installing Dagster guide in the docs for more information.
create_repository_using_definitions_args has been added for users to backport their repository definitions to the new Definitions API
When running Dagit on your local machine, a prompt will now appear that allows you to optionally enter an email address to receive Dagster security updates or subscribe to the Dagster newsletter. This prompt can be dismissed in the UI, or permanently disabled by adding the following to your dagster.yaml file:
nux:
enabled: false
The grpcio pin in Dagster to <1.48.1 has been restored for Python versions 3.10 and 3.11, due to upstream issues in the grpcio package causing hangs in Dagster.
[dagit] Improved query performance on Scheduled Runs page.
[dagit] The "Materialize" button now allows you to add tags to asset materialization runs. If your assets do not require config or partitions, you may need to shift-click "Materialize".
[dagit] The kind tags and logos shown on assets in the Asset Graph now appear in other parts of Dagit so it's easier to understand your assets.
[dagit] Selecting a materialization event on the Asset Details page now shows links to the upstream materialzations ("Source Data") that were incorporated into that version of the asset.
[dagit] Added or improved document (browser tab) titles throughout Dagit.
[dagster-snowflake] Snowflake resource and IO manager now support private key authentication with unencrypted keys
[dagster-dbt] The op created when using load_assets_from_dbt* is now configurable, allowing you to pass in specific parameters to the underlying dbt command (such as --full-refresh). To do so, supply config of the form {"ops": {"run_dbt_<abcde>": {"config": {"full_refresh": True}}}} when defining your asset job, or in Dagit.
For time-partitioned assets, the build_asset_reconciliation_sensor will now only materialize partitions from the past day. Previously, if a new asset was added with a large number of missing partitions, a run for each of the missing partitions would be launched immediately.
A variety of performance improvements to the build_asset_reconciliation_sensor, which should help significantly speed up sensor evaluation in cases where there is a large number of assets or partitions.
[dagit] Fixed broken code location names in the “Definitions” filter dialog accessible from the left navigation.
[dagit] The Backfills pages in Dagit no longer crash when your backfills span tens of thousands of partition keys
[dagit] The asset graph now links to the failed run, not the last successful materialization, when assets are shown in a "Failed" state.
The selection argument of define_asset_job now accepts lists of AssetKeys or AssetsDefinitions.
RunRequest now takes a stale_assets_only flag that filters the full set of assets that would be materialized by a job to stale assets only. This can be used in schedules and sensors.
Dagit will now choose a different open port on the local machine to run on when no port is specified to the dagit command and the default port 3000 is already in use.
The grpcio pin in Dagster to <1.48.1 has been removed for Python versions 3.10 and 3.11. Python 3.7, 3.8, and 3.9 are still pinned to <1.48.1 due to a bug in the grpc library that is causing the process to sometimes hang.
When it is likely that an op process was killed due to running out of memory, a clearer error message is now displayed in Dagit.
When a sensor tick fails due to taking longer than 60 seconds to execute, a clearer error message is displayed on the sensor timeline in Dagit.
When you view compute logs on a run in Dagit, we now locally track whether you choose the stdout or stderr tab. The next time you view compute logs, you will see that tab first by default.
The executor and loggers arguments on Definitions are no longer experimental.
[dagster-dbt] When json_log_format is set to False when using the dbt_cli_resource, logs will be emitted at the appropriate log level in some situations. Previously, all logs would be emitted at the INFO level.
[dagster-snowflake] The Snowflake IO Manager and Snowflake Resource now support private key authentication. Thanks Josh Taylor!
[dagster-airbyte] Users can now specify freshness policies when generating Airbyte assets.
[dagster-airbyte] When using managed Airbyte ingestion, users can now specify a destination table prefix.
Fixed a bug that caused backfills launched from the asset graph page not to work with code locations running versions of Dagster less than 1.1.8.
Fixed a bug that reverted to the default partition mappings in situations where asset dependencies were resolved based on group instead of asset key.
The way skips are propagate through the graph when using dynamic outputs are used has been fixed.
Fixed a bug affecting the download link for cloud-based compute log manager implementations (e.g. dagster-azure / dagster-aws / dagster-gcp)
Fixed a bug that would cause errors when using build_asset_reconciliation_sensor with asset graphs that contained references to source assets without the associated SourceAsset objects (which may happen when using load_assets_from_dbt_*).
[dagit] Fixed an issue where an error appeared in dagit when a code server stopped and restarted.
[dagit] Previously, when restarting the dagit process, the Dagit frontend kept cached versions of certain queries even after the code location finished loading. This could lead to display of stale versions of jobs or other code objects. These objects will now be correctly retrieved anew from the backend.
[dagster-dbt] Fixed a bug with the DbtManifestAssetSelection which could result in KeyErrors when selecting from projects with sources defined.
[dagster-k8s] Fixed a bug where disabling run worker crash recovery by setting maxResumeRunAttempts to 0 in the Helm chart had no effect.
[dagster-airflow] Fixed a bug where transformed Airflow DAG schedules would always use UTC for their timezone.
[dagit] The /instance and /workspace path prefixes were removed in previous version, but redirects were left in place. These redirects have now been removed.
The new StaticPartitionMapping enables explicitly defining the dependencies between partitions in two StaticPartitionsDefinitions. Thanks Alexander VR!
Fixed a typo in the Dagster Instance documentation header - thanks Cushnir Grigore!
Fixed a typo in the Dagster Instance documentation body - thanks Chris Zubak-Skees!
Fixed docstring for static_partitioned_config - thanks Sylvain Lesage!
Fix dead link in the docs to the Slack community - thanks Emil Christensen!