Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Unpin bluesky once all Ophyd devices used in plan_stubs are of appropriate type #828

Closed
DiamondJoseph opened this issue Oct 9, 2024 · 1 comment
Closed

Unpin bluesky once all Ophyd devices used in plan_stubs are of appropriate type #828

DiamondJoseph opened this issue Oct 9, 2024 · 1 comment
Labels
dependencies Pull requests that update a dependency file

Comments

@DiamondJoseph
Copy link
Contributor

Bluesky 1.13 contains changes to the plan_stubs exported from bluesky that they now required devices to comply to the protocols defined in bluesky. However, the devices in Ophyd do not comply to the bluesky protocols: see Ophyd issue.

If we can move the remaining devices- * that are used directly with bluesky plan_stubs, not with bluesky plans *- to Ophyd-async, or resolve the issue with Ophyd devices and type-checked Bluesky plan stubs, we can update to Bluesky 1.13

Acceptance Criteria

CI passes with Bluesky 1.13
@DiamondJoseph DiamondJoseph added the dependencies Pull requests that update a dependency file label Oct 9, 2024
@DiamondJoseph
Copy link
Contributor Author

Irrelevant due to #830

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
dependencies Pull requests that update a dependency file
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@DiamondJoseph