-
Notifications
You must be signed in to change notification settings - Fork 804
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
Kraken: Fix wsCancelOrders not erroring with order id #1505
Kraken: Fix wsCancelOrders not erroring with order id #1505
Conversation
1b26681
to
f34ffc6
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The cancel orders change works well 🎉
I'm not liking those failures in kraken's |
TestWsOpenOrders errors were unrelated. This is good to review. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for making those changes! tACK!
As an extra, would you consider this diff? Otherwise, I can just put on another PR. I just wanted to get rid of the func setupWsTests
while I was here
Already in the next upcoming branch. I've got significant testing of Subscribe in there without mocking, so I'm on the fence about adding a mock for it if we don't have to ( perversely ). Anyway, Let's touch on this when that PR lands. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good stuff. tACK.
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #1505 +/- ##
==========================================
- Coverage 37.83% 36.02% -1.82%
==========================================
Files 411 411
Lines 147204 176906 +29702
==========================================
+ Hits 55699 63728 +8029
- Misses 83733 105391 +21658
- Partials 7772 7787 +15
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Changes are lovely. Thanks.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice work
ebf4876
to
1849749
Compare
Rebased and ready to roll 😄 |
ebf4876
to
bc84123
Compare
We were using the "cancel many" facility of the Kraken api. However since that doesn't actually report errors individually, it seems saner to just multiplex over it. We were going to get N+ responses anyway. Might as well send N+ requests
bc84123
to
e7e5a5e
Compare
We were using the "cancel many" facility of the Kraken api. However since that doesn't actually report errors individually, it seems saner to just multiplex over it.
We were going to get N+ responses anyway. Might as well send N+ requests
One thing I'm unhappy about is the change of Key/Secret for this to work.
I really don't like that there's special values for the auth values which get silently ignored, such as Test, Mock, Key, Secret, etc.
So I've ended up using something adhoc, and putting a require in the test to ensure it's obvious if the auth-conn isn't connected.
Type of change
How has this been tested