3.0.0

Backwards-incompatible changes

• Cancelling or aborting jobs is not supported by the combination of arq and sync worker functions. Properly reflect this in job metadata by forcing execution duration to 0 to indicate that no limit is applied. Substantially increase the default arq job timeout since the timeout will be ineffective anyway.
• Drop the CUTOUT_TIMEOUT configuration option since we have no way of enforcing a timeout on jobs.
• Upgrade the base image for the backend worker to the latest weekly. This includes a new version of lsst.daf.butler, which targets a new version of the Butler server with a backwards-incompatible REST API.

New features

• Support human-readable 4h30m20s-style strings for CUTOUT_LIFETIME and CUTOUT_SYNC_TIMEOUT in addition to numbers of seconds.

Other changes

• Unknown failures in the worker backend are now recorded as fatal UWS errors rather than transient errors. This is the more conservative choice for unknown exceptions.

What's Changed

• DM-44763: Take advantage of class serialization by @rra in #170
• DM-44763: Refactor the UWS support library by @rra in #171
• DM-44763: Drop vo-cutouts run command by @rra in #172
• DM-44763: Move runid handling to a dependency by @rra in #173
• DM-44763: Reflect the lack of job cancellation support by @rra in #174
• DM-44763: Document constraints when adding handlers by @rra in #175
• DM-44763: Fix typing of retry_async_transaction decorator by @rra in #176
• DM-44763: Stop using db_session_dependency in UWS by @rra in #177
• DM-44763: Support human-readable timedelta strings by @rra in #178
• DM-44763: Move logging to the service layer by @rra in #179
• DM-44763: Refactor worker exception handling by @rra in #180
• DM-44503: Bump science pipelines stack for new Butler by @dhirving in #181
• Collect fragments for new release by @athornton in #182

New Contributors

• @athornton made their first contribution in #182

Full Changelog: 2.0.0...3.0.0