Sourced from dagster's changelog.

1.5.11 / 0.21.11 (libraries)

New

• [ui] Asset graph now displays active filters.
• [ui] Asset graph can now be filtered by compute kind.
• [ui] When backfilling failed and missing partitions of assets, a “Preview” button allows you to see which ranges will be materialized.
• [dagster-dbt] When running DAGSTER_DBT_PARSE_PROJECT_ON_LOAD=1 dagster dev in a new scaffolded project from dagster-dbt project scaffold, dbt logs from creating dbt artifacts to loading the project are now silenced.
• [dagster-airbyte] Added a new connection_meta_to_group_fn argument which allows configuring loaded asset groups based on the connection’s metadata dict.
• [dagster-k8s] Debug information about failed run workers in errors surfaced by run monitoring now includes logs from sidecar containers, not just the main dagster container.

Bugfixes

• The QueuedRunCoordinatorDaemon has been refactored to paginate over runs when applying priority sort and tag concurrency limits. Previously, it loaded all runs into memory causing large memory spikes when many runs were enqueued.
• Callable objects can once again be used to back sensor definitions.
• UPathIOManager has been updated to use the correct path delimiter when interacting with cloud storages from a Windows process.
• In the default multiprocess executor, the STEP_WORKER_STARTED event now fires before importing code in line with the other executors.
• During execution, skipping a step now takes precedence over “abandoning” it due to upstream failure. This is expected to substantially improve the “retry from failure” workflow when conditional branching is in use.
• Fixed an issue where default config values set to EnvVar did not work properly.
• Fixed an issue where resources which implemented IAttachDifferentObjectToOpContext would pass the incorrect object to schedules and sensors.
• Fixed a bug that caused auto-materialize failures when using the materialize_on_cron rule with dynamically partitioned assets.
• Fixed an issue where sensor ticks would sporadically fail with a StopIteration exception.
• [ui] For a job launchpad with a large number of tabs, the “Remove all” option was pushed offscreen. This has been fixed.
• [ui] The asset backfill page now correctly shows backfills that target only unpartitioned assets.
• [ui] Launching an asset job that was defined without_checks no longer fails by attempting to include the checks.
• [dagster-databricks] fix bug that caused crash when polling a submitted job that is still in the Databricks queue (due to concurrency limit).

Community Contributions

• Patched issue where the local compute log path exposed file content outside of the compute log base directory - thanks r1b!
• [dagster-databricks] Added ability to authenticate using an Azure service principal and fix minor bugs involving authenticating with a service principal while DATABRICKS_HOST is set. Thanks @​zyd14!

Experimental

• [ui] Dark mode is now available via the User Settings dialog, currently in an experimental state. By default, the app will use a “legacy” theme, closely matching our current colors. A new light mode theme is also available.
• [ui] Asset graph group nodes can be collapsed/expanded by right clicking on the collapsed group node or the header of the expanded group node.
• [ui] Asset graph group nodes can be all collapsed or all expanded by right clicking anywhere on the graph and selecting the appropriate action.
• [ui] The tree view was removed from the asset graph.
• [pipes] PipesLambdaClient, an AWS Lambda pipes client has been added to dagster_aws.
• Fixed a performance regression introduced in the 1.5.10 release where auto-materializing multi-assets became slower.

Documentation

• [getting-started] Added an overview to the Getting Started section that explains the whats and whys of Dagster.
• [pipes] Added a guide for using the new PipesLambdaClient with Dagster Pipes.
• [getting-started] Simplified the Getting Started category. The following pages have been moved:
  • Understanding Dagster project files is now in Guides
  • Telemetry is now in About
• [guides] Fixed a broken link in the Airflow-to-Dagster concept mapping guide.
• [deployment] Cleaned up and updated the Executing with Celery OSS deployment guide.

... (truncated)

• 0e53326 1.5.11
• 7da6fd8 Changelog 1.5.11 (#18577)
• 349f370 Fix legacy graph background (#18559)
• f2882dd Update toggle style (#18544)
• 6a380c1 Bump asset backfill log from debug to info level (#18519)
• 44e2d75 [AssetGraph] cycle-safe get_ancestors (#18516)
• 40c8e9f [ui] Fix nav expansion button colors (#18518)
• 4637e98 Extract run concurrency content to be reused by cloud concurrency page (#18438)
• 60af95d feat(dbt): make dbt parse quiet in a scaffolded project (#18501)
• 1962b17 [Asset graph] Fix infinite loop when there are no kind tags (#18509)
• Additional commits viewable in compare view

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  You can disable automated security fix PRs for this repo from the Security Alerts page.