-
Notifications
You must be signed in to change notification settings - Fork 184
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
Identify incomplete processing in OQC server helper #780
Conversation
Command Bot: Processing... |
CUDA Quantum Docs Bot: A preview of the documentation can be found here. |
Thanks, @owen-oqc. Do you think this change can explain these two nightly integration test failures?
The error for those runs looked like this: [2023-09-29 03:28:12.135] [info] [OQCServerHelp.cpp:267] Null results received; fetching detailed error message here: https://sandbox.qcaas.oqc.app/tasks/225a5665-264f-4730-8400-e1cb10c3fc07/error
terminate called after throwing an instance of 'std::runtime_error'
what(): OQC backend error message: {"task_error":null}
/__w/_temp/54c4d008-0960-46fa-b317-d7d26c92b688.sh: line 10: 5857 Aborted (core dumped) ./a.out |
Yes exactly this |
Great! If you merge the latest from main into your branch, we can get this merged after that. |
json null previously matched against c++ NULL 0. This allowed the future to terminate and fetch results before processing had finished.
4cdcdc8
to
cb81486
Compare
Command Bot: Processing... |
json null previously matched against c++ NULL 0. This allowed the future to terminate and fetch results before processing had finished.
Description