-
## Expected Behavior
If I import bluesky plan stubs in my queueserver startup file, they should be available in the queueserver as plans. This was the behavior when using bluesky v1.13.0a3 …
-
During this import: https://github.com/aps-8id-dys/bluesky/blob/af8ca959eb5032fda622f2be6d1878f70caebeda/scripts/bs_qs_startup.py#L23
there are imports such as `from ..initialize_bs_tools import ..…
-
Humble thought that I don't have time to implement.
It seems like there is increasing interest in being able to identify which objects which objects in a namespace are plans. See #1476 and `bluesky…
-
## Expected Behavior
In version 1.13.0a3, passing plan stubs to [inspect.](`https://docs.python.org/3/library/inspect.html#inspect.isasyncgenfunction`) returns true.
```python
In [3]: f…
-
The [bluesky-queueserver](https://github.com/bluesky/bluesky-queueserver) and associated projects have staked out a good scope for a full-featured "RunEngine as a service". To use it, users have to ta…
-
I am running the queue server in a docker container and following along with the tutorial for the queue server. My startup code is simply the startup code in the ophyd-async tutorial (https://blueskyp…
-
This is not a package issue per se; it’s a bluesky integration consideration that converges at the queueserver. I want to capture a discussion in progress, and we could move this to a more appropriate…
-
I noticed in our queueserver-driven acquisitions from this weekend, the `experimenter` field in the metadata is set to "Bruce Ravel" instead of the user list from the SAFS form
I think this has to …
-
## Expected Behavior
When using native python type hints with the standard `bluesky.plans`, plans should prepare successfully
## Current Behavior
This behavior varies depending on the plan annota…
-
## Expected Behavior
Our Kafka servers are secured using SSL and SASL. We wish to supplying the required parameters to the Queueserver's in built Bluesky-Kafka Publisher instance (via the `producer_c…