-
Notifications
You must be signed in to change notification settings - Fork 465
OrderWatcher returns an error and stop working after that #1710
Comments
Thanks for reporting this issue @valkyriaivan. This looks to me like a potential race-condition. Will work on confirming that hunch and fixing the issue. |
@fabioberger Any updates on this issue? Was it confirmed your hunch? I'm just curious to know if it is a problem from my integration. |
I have updated the order watcher to 4.0.5 and a similar error keeps happening, now it gives more info about the error so I'll provide it in case it helps. It seems to be an internal error since it is never returned in the callback.
|
Thanks for reporting @valkyriaivan. Looked into this second issue and it is indeed another race condition. I've opened a PR with a fix. |
Fixed it. Going to publish a new version of the package in the next day or two. |
Expected Behavior
The orderWatcher should do the callback without errors when and order is expired.
Current Behavior
The orderWatcher returns an error and stops checking the orders status after that, even if more orders are added.
Steps to Reproduce
I can't reproduce the error since it happens at random times during the cycle.
Context
I create orders every 30 minutes for some days and the orderWatcher delete those when they expire. After sometimes 2-3 hours or a day(it's not arbitrary), an error is given by the subscribe callback and the watcher stops checking the orders status.
I checked the orders before adding them and they are fine. The orders are created from a bot, so it's not imput human error
Your Environment
The text was updated successfully, but these errors were encountered: