Skip to content

Releases: DiamondLightSource/blueapi

0.4.0: General improvements and tidying

27 Feb 10:14
ee66aae

Choose a tag to compare

What's Changed

Full Changelog: 0.3.15...0.4.0

0.3.15-alpha1

13 Feb 14:03

Choose a tag to compare

0.3.15-alpha1 Pre-release
Pre-release

Another waste of my life

0.3.15-alpha0

13 Feb 13:49

Choose a tag to compare

0.3.15-alpha0 Pre-release
Pre-release

Further Template fixes

0.3.15-dev0

09 Feb 13:58

Choose a tag to compare

Basic Open Telemetry support for test

0.3.15a0

13 Feb 13:49
598d789

Choose a tag to compare

0.3.15a0 Pre-release
Pre-release

What's Changed

Full Changelog: 0.3.15...0.3.15a0

Test Release

13 Feb 14:25
598d789

Choose a tag to compare

Test Release Pre-release
Pre-release

What's Changed

Full Changelog: 0.3.15...0.3.15-a0

0.3.15

14 Nov 16:53
b30dda7

Choose a tag to compare

What's Changed

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

10 Nov 14:19
d50a439

Choose a tag to compare

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

02 Nov 16:14
db8b681

Choose a tag to compare

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

31 Oct 10:21
e3c4a78

Choose a tag to compare

What's Changed

Full Changelog: 0.3.11...0.3.12