v2.4.13

Improvements

Database table trigger versioning

This release changes the naming of table triggers that the ui_backend sets up to include a timestamp as a version. This allows the backend to recreate table triggers in case any changes need to be deployed, or skip in case of a version match.

⚠️ After deploying this version of the service, do note that in the case of a service rollback, the database will have duplicate table triggers due to older service versions not having any cleanup code for these. In such a case, clean up the remaining triggers manually

Reduced Postgres notify messaging

This release reduces the volume of pg_notify messages that the database sends on table events. There should not be any effect on the average deployment, but for very large deployments running on services like Amazon Aurora, this solves significant performance issues.

Fixes runs starting with a failed status in certain cases

This release fixes an issue with runs starting with a failed status if the Metaflow client version being used had an uncommon version string.

What's Changed

• fix: linting issues by @saikonen in #433
• feature: version table triggers by @saikonen in #432
• fix: log paths failure by @saikonen in #430
• Bump azure-identity from 1.10.0 to 1.16.1 in /services/ui_backend_service by @dependabot in #425
• fix: reduce postgres notify messaging by @saikonen in #409
• fix: correctly sort log lines based on utc_tstamp by @saikonen in #435
• fix: make trigger cleanup schema aware by @saikonen in #436
• fix: version string parse failure leads to runs starting without a heartbeat by @saikonen in #443
• fix: run status stuck as failed with heartbeat changes by @saikonen in #441
• feature: treat client version parse failures as heartbeat-enabled by default by @saikonen in #444
• fix: incorrect table name passing in notify broadcast by @saikonen in #446
• release: 2.4.13 by @saikonen in #447

New Contributors

• @dependabot made their first contribution in #425

Full Changelog: v2.4.12...v2.4.13