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
{{ message }}
This repository has been archived by the owner on May 13, 2022. It is now read-only.
I encountered a situation that caused the new-yieldgen-algo.py maker bot to crash. Reviewing the logs, I believe this was the flow - I can provide full logs by request if someone wants to look into this further.
takerA fills order which used oid 4, mixdepth 3
order is filled and propagated normally, utxos removed properly, afaict
neworders shows 1 through 4, oldorders shows 1 through 5
new_old_diff and old_new_diff only show 4, (no oid5!). can_orders is empty, ann_orders shows oid 4
5 is not removed when new orders are announced
takerB fill order which used oid 4, mixdepth 0
order is filled and propagated normally, utxos removed properly, afaict
neworders shows 1 through 3, oldorders shows 1 through 5 still, with 4 and 5 now overlapping maxsize
new_old_diff and old_new_diff do not show any changes, can_orders is empty, ann_orders is empty
takerC fills order which used oid 4, mixdepth 0
maker bot crashes with Exception: Not enough funds
I reviewed some old logs for the new-yieldgen-algo bot, and discovered that can_orders has never returned anything other than empty, from what I found. It seems I just never had the required fill flow to create this situation previously, as the ann_orders were lucky enough to replace the uncancelled oids most of the time.
From comparing maker bot methods, I think something is buggy in these lines. I am testing a fix to use the method in #99 instead and will update this issue accordingly.
The text was updated successfully, but these errors were encountered:
Your code is shorter. I think there was a reason I rewrote it into the far longer method currently used. I don't remember the reason though, maybe it was nothing, or probably just something aesthetic.
added commit dc1aa21
I believe this bug arose because of a bad way of comparing lists of orders (using zip()) which failed when the lists were of unequal length.
Also changed some of the variable names to make it slightly easier to understand.
Not tested in depth
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I encountered a situation that caused the new-yieldgen-algo.py maker bot to crash. Reviewing the logs, I believe this was the flow - I can provide full logs by request if someone wants to look into this further.
I reviewed some old logs for the new-yieldgen-algo bot, and discovered that can_orders has never returned anything other than empty, from what I found. It seems I just never had the required fill flow to create this situation previously, as the ann_orders were lucky enough to replace the uncancelled oids most of the time.
From comparing maker bot methods, I think something is buggy in these lines. I am testing a fix to use the method in #99 instead and will update this issue accordingly.
The text was updated successfully, but these errors were encountered: