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 canceling an order, the adapter looks for the payload to equal OK. Line 283 - GDAX Exchange Adapter
It should be looking for the ReasonPhrase, as I have corrected below. :) if (response.getReasonPhrase().equalsIgnoreCase("OK")) { return true; } else { final String errorMsg = "Failed to cancel order on exchange. Details: " + response; LOG.error(errorMsg); return false; }
I'm not too familiar with patching other peoples projects on Github, so not really sure where to start with that. Im going to look into it for next time! Anyway, the fix is above! :)
The text was updated successfully, but these errors were encountered:
GDAX adapter was returning incorrect cancel order status despite the order being cancelled successfully.
The Exchange API was changes to return orderId in response payload - the adapter code was out of date. Thanks for @Gondee for reporting this.
Also bumped up versions for next RC candidate.
Good spot Josh, nice one. The adapter code was out of date. GDAX now return the cancelled orderId in the payload instead of 'OK'. Code fixed and integration tests pass. Also running on GDAX now and cancelling fine.
On canceling an order, the adapter looks for the payload to equal OK.
Line 283 - GDAX Exchange Adapter
It should be looking for the ReasonPhrase, as I have corrected below. :)
if (response.getReasonPhrase().equalsIgnoreCase("OK")) { return true; } else { final String errorMsg = "Failed to cancel order on exchange. Details: " + response; LOG.error(errorMsg); return false; }
I'm not too familiar with patching other peoples projects on Github, so not really sure where to start with that. Im going to look into it for next time! Anyway, the fix is above! :)
The text was updated successfully, but these errors were encountered: