-
Notifications
You must be signed in to change notification settings - Fork 267
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
OrderWatcher issue #26
Comments
@amirh3n thanks for opening an issue. Did you fill the order in it's entirety? |
@fabioberger Yes, and another thing which i forgot to mention was I'm getting also expired orders from API |
What API? Radar? If so, that is a known issue with their SRA implementation. |
@fabioberger No, I use |
I see, that is definitively a bug. We will try and get a fix out soon. If you want to attempt to fix it, we'd be happy to accept a pull request. |
This is likely a result of the issue described in #28. |
There are several other issues going on in the orderwatcher and the pruning functionality as well. A few of the issues
|
I still have pruning issues... FULLY_FILLED orders such as this one: Status from codesandbox: https://imgur.com/a/s6x9MvM |
Thanks for letting us know about these issues @pelsasser, @amirh3n and @michaelhly. Working on a PR to address all of them. |
Issues have been fixed in #44 |
Hello,
I add order using
/v2/order
api and i fill the order from my application but the order is still returned from/v2/orderbook
APIThe text was updated successfully, but these errors were encountered: