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

IBM rest API communication issues #29

Closed
eugescu opened this issue Apr 10, 2018 · 1 comment
Closed

IBM rest API communication issues #29

eugescu opened this issue Apr 10, 2018 · 1 comment

Comments

@eugescu
Copy link

eugescu commented Apr 10, 2018

Below are two examples of HTTP status line issues I have encountered in the last 24 hrs.

EX1:
Job Response: RUNNING[2018-04-09 16:51:12.680] [xacc-logger] [info] IBM Accelerator caught exception while calling restClient->get() - Failed to read HTTP status line
[2018-04-09 16:51:12.680] [xacc-logger] [info] Retrying HTTP Get.
Job Response: RUNNINGAssertion failed: (false), function operator[], file /Users/edq/Library/Python/3.6/lib/python/site-packages/xacc-0.1.0-py3.6-macosx-10.11-x86_64.egg/include/rapidjson/include/rapidjson/document.h, line 1103.
Abort trap: 6

EX2:
----> 1 energy = lambda angles: vqe.execute(xaccOp, **{'task':'compute-energy', 'ansatz':IR_fun, 'accelerator':acc, 'vqe-params':str(angles)[1:len(str(angles))-1]
2 })
RuntimeError: Failed to read HTTP status line

@amccaskey
Copy link
Contributor

Ex1 makes me wonder if IBM updated their JSON string for checking job status...

sethrj pushed a commit to sethrj/xacc that referenced this issue Jul 31, 2024
Fixed tpls/CmakeLists.txt to bypass cpr if remote accelerators are disabled
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

No branches or pull requests

2 participants