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.

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

Ophyd v2: add _exception to AsyncStatus to propagate errors through FailedStatus. #1103

Merged
merged 13 commits into from
Apr 12, 2023

Conversation

rosesyrett
Copy link
Contributor

added ._exception to AsyncStatus to match with method in v1 Status object

Solves #1098

This will be followed by a PR in bluesky, which will change the Status object that ophyd v2 AsyncStatus inherits from as well as how FailedStatus gets instantiated. Once I have done this, I will link it here so the changes can be viewed together.

@tacaswell
Copy link
Contributor

Per matplotlib/matplotlib#25406 we should at have a think about keeping a reference to the exception. I think in this case we (and the v1 status objects) we want to do this so we can move the exceptions around, but we should be sure.

ophyd/v2/core.py Outdated Show resolved Hide resolved
ophyd/v2/core.py Outdated Show resolved Hide resolved
@rosesyrett
Copy link
Contributor Author

At this point, I think I've tested every line I've added in the ophyd v2 core.py file... Should I write some more tests for anything else? Maybe for the v1 part?

@coretl coretl merged commit d9d3331 into master Apr 12, 2023
@coretl coretl deleted the propagate_exception_into_failed_status branch April 12, 2023 09:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants