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
Handle random remote disconnects? #229
Comments
All signs point to web server configuration error, since the problem can not be reproduced after server config upgrade. For other deployments, this might help: https://stackoverflow.com/a/47077330/404556. The alternative of client-side-instructed preemptive connection closing (sending |
Possible cause: psf/requests#4664. Implementing #414 should serve as a workaround here. |
Reopening until fix from #414 is verified. |
Changes since 0.8.2: New Features --- - All SAPI requests retried whenever possible, controlled with new `http_retry_*` Client options (#414) - Introduced `SAPIError` base exception with SAPI error message and code, other exceptions reorganized in a backwards-compatible way - Support for problem labels: `sample_*` methods accept optional `label` kwarg, and `Future.sampleset.info` contains `problem_label` (#444) - Switched to CircleCI (#119) Fixes --- - Handle remote disconnects in an edge case (#229)
This is a traceback from a
dwave-system
integration test (Python 3.4 on OS X):The reason could be related to SAPI webservice Keep-Alive timeouts: server closes connection, and client tries to write while not realising the connection (http session) is closed.
In that case we could retry on
BadStatusLine
, orRemoteDisconnected
(in py3.5+).The text was updated successfully, but these errors were encountered: