Test Release

What's Changed

• Fix shutdown by @abbiemery in #335
• Extract handler methods to ABC by @joeshannon in #342
• Add try except to messaging connection by @abbiemery in #345
• Adapt to Black 24 by @joeshannon in #358
• Run BlueskyContext and Worker in subprocess by @joeshannon in #343
• Remove reference to deleted devcontainer documentation by @callumforrester in #373
• Remove parameter caching inside task class by @callumforrester in #370

Full Changelog: 0.3.15...0.3.15-a0

0.3.15

What's Changed

• Update pyproject.toml by @rosesyrett in #336

This release will actually publish to pypi, because we no longer depend on main branch versions of ophyd-async and bluesky. See the changelogs for their releases (0.2.0 and 1.12 respectively) for more details on the subsequent changes to this package, due to these dependency updates.

Full Changelog: 0.3.14...0.3.15

Configurable status updates and listener

Changes in this release:

-> Remove listener pod

Change helm deployment so we don't spin up a pod in the blueapi
deployment that just listens to documents.
At the moment, a deployment using release 0.3.14 fails due to
securityContext issues, which when fixed still seem to cause problems.
This should be investigated in future.

-> Add configuration option to disable status updates via message bus

As well as data documents, blueapi produces events when the status
objects monitored by the run engine are updated. These events are useful
for creating progress bars and similar updates. Unfortunately it seems
very easy to unintentionally make plans/devices produce a very large
number of these updates. The handling of all of these results in log
spam and high CPU usage.

We're seeing this now on I22 and have seen similar problems before (see
#111). I think the easy way to make debugging easier is to make the
status update handling optional and easy to turn off via config. To that
end...

Changes:

Add config option to disable status events
Make the worker only hook into the run engine if this option is marked
as true

-> Add Document Listener

Add CLI command to listen for documents from the message bus and print
them to the console. Also add it to helm deployment for blueapi

-> Allow passing kwargs to make_all_devices for dodal modules (again)

Functionality added in
#304 and being used
in
hyperion
got removed in
076da45
. It doesn't look like there was a clear reason for this removal of
functionality so I think it should be reinstated.

-> Pin fastapi to <0.99 to use openapi <3.1

Configure containerPath for mounted volume

Previously, the startup script for blueapi forced any mounted volumes to be mounted in /blueapi-plugins/scratch. This makes a change to that, and allows the mounted volume path in the container (i.e. the containerPath) to be configurable.

This release should build the container with the latest version of bluesky from main, which includes a bug fix: bluesky/bluesky#1627

Support host network

What's Changed

• Add option to helm chart to run on host network by @callumforrester in #326

Full Changelog: 0.3.11...0.3.12

0.3.11 Use numtracker service to determine data session

What's Changed

• Reintroduce VisitDirectoryProvider and update in preprocessor by @rosesyrett in #325

Full Changelog: 0.3.10...0.3.11

Fix plan preprocessor

Patches an issue with the last release, where due to bluesky using generator functions as coroutines writing a preprocessor that loops through the messages that should be sent to the run engine and adding intermittent logic does not work as expected.

See bluesky/bluesky#1625

0.3.9 Better connect error message

What's Changed

• Make devices connect with a timeout by @callumforrester in #321

Full Changelog: 0.3.8...0.3.9

0.3.8 Use bash script to handle scratch

What's Changed

• Use external service to configure ophyd-async detector data writing by @callumforrester in #315
• Move scratch management to bash script by @callumforrester in #320

Full Changelog: 0.3.7...0.3.8

0.3.7 Sort out vevnv permissions

Alter permissions of venv and cache (#318)