search

catalyst-cooperative / pudl-usage-metrics

A dagster ETL for collecting and cleaning PUDL usage metrics.
MIT License
1 stars 0 forks source link

Bump dagster from 0.14.9 to 0.14.19 #15

Closed dependabot[bot] closed 2 years ago

dependabot[bot] commented 2 years ago

Bumps dagster from 0.14.9 to 0.14.19.

Release notes

Sourced from dagster's releases.

0.14.19 (June 3, 2022)

New

  • Metadata can now be added to jobs (via the metadata parameter) and viewed in dagit. You can use it to track code owners, link to docs, or add other useful information.
  • In the Dagit launchpad, the panel below the config editor now shows more detailed information about the state of the config, including error state and whether the config requires further scaffolding or the removal of extra config.
  • FileCache is now marked for deprecation in 0.15.0.
  • In Dagit, the asset catalog now shows the last materialization for each asset and links to the latest run.
  • Assets can now have a config_schema. If you attempt to materialize an asset with a config schema in Dagit, you'll be able to enter the required config via a modal.

Bugfixes

  • [helm] Fixed an issue where string floats and integers were not properly templated as image tags.
  • [dagster-k8s] Fixed an issue when using the k8s_job_executor where ops with long names sometimes failed to create a pod due to a validation error with the label names automatically generated by Dagster.
  • [dagster-aws] Fixed an issue where ECS tasks with large container contexts would sometimes fail to launch because their request to the ECS RunTask API was too large.

Breaking Changes

  • fs_asset_io_manager has been removed in favor of merging its functionality with fs_io_manager. fs_io_manager is now the default IO manager for asset jobs, and will store asset outputs in a directory named with the asset key.

Community Contributions

  • Fixed a bug that broke the k8s_job_executor’s max_conccurent configuration. Thanks @​fahadkh!
  • Fixed a bug that caused the fs_io_manager to incorrectly handle assets associated with upstream assets. Thanks @​aroig!

Documentation

  • [helm] Add documentation for code server image pull secrets in the main chart.
  • The Dagster README has been revamped with documentation and community links.

All Changes

https://github.com/dagster-io/dagster/compare/0.14.17...0.14.19

  • 9d14055 - Automation: versioned docs for 0.14.17 by @​elementl-devtools
  • d52d4cb - Revert "throw error for empty asset key ([#8069](https://github.com/dagster-io/dagster/issues/8069))" ([#8093](https://github.com/dagster-io/dagster/issues/8093)) by @​gibsondan
  • fab2e6e - [dagit] Launchpad: Show disabled "Scaffold" and "Remove" buttons instead of hiding them ([#8066](https://github.com/dagster-io/dagster/issues/8066)) by @​hellendag
  • b763dab - chore(buildkite): mention user in private channel ([#8071](https://github.com/dagster-io/dagster/issues/8071)) by @​rexledesma
  • 3d9ac9d - [asset-resources 2/n][rfc] io manager defs directly on asset defs ([#7920](https://github.com/dagster-io/dagster/issues/7920)) by @​dpeng817
  • b31b849 - docs: revamp the README ([#8052](https://github.com/dagster-io/dagster/issues/8052)) by @​rexledesma
  • 82a7a0c - 0.14.17 changelog ([#8083](https://github.com/dagster-io/dagster/issues/8083)) by @​smackesey
  • 9a14f45 - Fix upstream context handling in fs_asset_io_manager ([#8007](https://github.com/dagster-io/dagster/issues/8007)) by @​aroig
  • a558f1b - KnownState.ready_outputs ([#8016](https://github.com/dagster-io/dagster/issues/8016)) by @​alangenfeld
  • 5e6ba12 - chore: mark FileCache for deprecation in 0.15.0 ([#7922](https://github.com/dagster-io/dagster/issues/7922)) by @​rexledesma
  • c1fae94 - remove step stats query ([#8089](https://github.com/dagster-io/dagster/issues/8089)) by @​clairelin135
  • 1e06847 - migrate from deprecated sqlalchemy methods ([#7864](https://github.com/dagster-io/dagster/issues/7864)) by @​alangenfeld
  • c43efa9 - fix typos ([#8090](https://github.com/dagster-io/dagster/issues/8090)) by @​OwenKephart
  • 798eedc - Add skip for flaky grpc server test ([#8097](https://github.com/dagster-io/dagster/issues/8097)) by @​gibsondan
  • 2d3275c - chore(buildkite): ignore notifications on canceled builds ([#8099](https://github.com/dagster-io/dagster/issues/8099)) by @​rexledesma
  • beba51d - [dagit] Break apart LaunchpadSessionContainer ([#8101](https://github.com/dagster-io/dagster/issues/8101)) by @​hellendag

... (truncated)

Changelog

Sourced from dagster's changelog.

0.14.19

New

  • Metadata can now be added to jobs (via the metadata parameter) and viewed in dagit. You can use it to track code owners, link to docs, or add other useful information.
  • In the Dagit launchpad, the panel below the config editor now shows more detailed information about the state of the config, including error state and whether the config requires further scaffolding or the removal of extra config.
  • FileCache is now marked for deprecation in 0.15.0.
  • In Dagit, the asset catalog now shows the last materialization for each asset and links to the latest run.
  • Assets can now have a config_schema. If you attempt to materialize an asset with a config schema in Dagit, you'll be able to enter the required config via a modal.

Bugfixes

  • [helm] Fixed an issue where string floats and integers were not properly templated as image tags.
  • [dagster-k8s] Fixed an issue when using the k8s_job_executor where ops with long names sometimes failed to create a pod due to a validation error with the label names automatically generated by Dagster.
  • [dagster-aws] Fixed an issue where ECS tasks with large container contexts would sometimes fail to launch because their request to the ECS RunTask API was too large.

Breaking Changes

  • fs_asset_io_manager has been removed in favor of merging its functionality with fs_io_manager. fs_io_manager is now the default IO manager for asset jobs, and will store asset outputs in a directory named with the asset key.

Community Contributions

  • Fixed a bug that broke the k8s_job_executor’s max_conccurent configuration. Thanks @​fahadkh!
  • Fixed a bug that caused the fs_io_manager to incorrectly handle assets associated with upstream assets. Thanks @​aroig!

Documentation

  • [helm] Add documentation for code server image pull secrets in the main chart.
  • The Dagster README has been revamped with documentation and community links.

0.14.17

New

  • Added a pin to protobuf version 3 due to a backwards incompatible change in the probobuf version 4 release.
  • [helm] The name of the Dagit deployment can now be overridden in the Dagster Helm chart.
  • [dagit] The left navigation now shows jobs as expandable lists grouped by repository. You can opt out of this change using the feature flag in User Settings.
  • [dagit] In the left navigation, when a job has more than one schedule or sensor, clicking the schedule/sensor icon will now display a dialog containing the full list of schedules and sensors for that job.
  • [dagit] Assets on the runs page are now shown in more scenarios.
  • [dagster-dbt] dbt assets now support subsetting! In dagit, you can launch off a dbt command which will only refresh the selected models, and when you’re building jobs using AssetGroup.build_job(), you can define selections which select subsets of the loaded dbt project.
  • [dagster-dbt] [experimental] The load_assets_from_dbt_manifest function now supports an experimental select parameter. This allows you to use dbt selection syntax to select from an existing manifest.json file, rather than having Dagster re-compile the project on demand.
  • For software-defined assets, OpExecutionContext now exposes an asset_key_for_output method, which returns the asset key that one of the op’s outputs corresponds too.
  • The Backfills tab in Dagit loads much faster when there have been backfills that produced large numbers of runs.
  • Added the ability to run the Dagster Daemon as a Python module, by running python -m dagster.daemon.
  • The non_argument_deps parameter for the asset and multi_asset decorators can now be a set of strings in addition to a set of AssetKey.

Bugfixes

  • [dagit] In cases where Dagit is unable to make successful WebSocket connections, run logs could become stuck in a loading state. Dagit will now time out on the WebSocket connection attempt after a brief period of time. This allows run logs to fall back to http requests and move past the loading state.
  • In version 0.14.16, launching an asset materialization run with source assets would error with an InvalidSubsetError. This is now fixed.

... (truncated)

Commits


Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options
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 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)
dependabot[bot] commented 2 years ago

The following labels could not be found: dependencies.

dependabot[bot] commented 2 years ago

Superseded by #18.