You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On the upside, this may present an opportunity to finally implement retrying failed requests, without looking for a "flaky HTTP server" mock for tests first.
There are currently two implementations in the PR section that have been hanging there since the last time it was commonplace. (Note they're both against an earlier version of krakenex (v2.0.0, I believe), so both have merge conflicts.)
However, for 502 they would (should!..) return the same error as you're getting now - precisely for the reason that the behaviour can't be said to be deterministic, at least not without an arbitrarily long wait period (as described in the PSA).
Versions
What are you trying to achieve?
I want to addOrder via krakenex. It returns 502 error in response. So I re-send request later.
What do you expect to happen?
I expect that when krakenex return the 502 error, order won't be added in kraken.
What happens instead?
I saw duplicated order in my kraken.
I saw #66, however, I don't understand how can I avoid this.
The text was updated successfully, but these errors were encountered: