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

[FEATURE]: Error handling logic in .compute() functions #26

Open
coltonbh opened this issue Mar 3, 2022 · 0 comments
Open

[FEATURE]: Error handling logic in .compute() functions #26

coltonbh opened this issue Mar 3, 2022 · 0 comments
Assignees
@coltonbh
Labels
enhancement New feature or request

Comments

@coltonbh
Copy link
Contributor

coltonbh commented Mar 3, 2022

I currently have no error handling logic for failed compute operations.

I presume that I'd want the .compute() method on each client to return Union[AtomicInput, FailedOperation] and to properly construct a FailedOperation result if the input was rejected or caused the server to crash.

Currently this isn't a big deal in QCEngine because exceptions are handled by the .compute() wrapper. However, if I want a nicer interface for end users of the tcpb-client package returning a FailedOperation object would be more QCSchema compliant.
@coltonbh coltonbh self-assigned this Mar 3, 2022
@coltonbh coltonbh added the enhancement New feature or request label Mar 3, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@coltonbh coltonbh

Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@coltonbh