Handling ConnectionError, HTTPError thrown during a query about python3-krakenex HOT 3 CLOSED

For those who encounter the same problem, I found the solutions in PRs #99 and #100 were insufficient to prevent the program from crashing. My approach was instead to wrap the price querying code in a shell script that restarts upon failure, which seems to work great although it doesn't solve the underlying problem at the krakenex level.

Closing. Thank you for the input!

from python3-krakenex.

Is this a problem on the kraken side?

More often than not. You can avoid a few 'Connection reset by peer' by sending less queries. However, during a DDoS or heavy load Kraken may choose to drop/reset the connection regardless.

It can also happen due to a flaky connection.

Does it require resetting / opening a new connection through krakenex and closing the current session?

See the approaches in PRs #99 and #100, as well as the issues linked there, for a three-year old (:disappointed:) discussion on this.

I never got to merging either approach into the package, since both solutions have issues, and are hard to test properly these days.

Github says either of those can still be merged into the code as-is.

Something else?

Be careful with retries:

https://www.reddit.com/r/krakenex/comments/778uvh/psa_http_error_502_does_not_mean_the_query_wont/

This is old, and Kraken has had an iteration on their production code, so the PSA may not apply verbatim - just linking as an example of "unexpected things can happen".

from python3-krakenex.

Marking as duplicate of issue #66, mainly because the solution seems to be the same. Ping back if I misunderstood.

from python3-krakenex.