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
I ran into an edge case that might be a simple fix if you have a few minutes you are mad at. It's not a critical issue, but I will leave it here anyway.
I have a smaller bot I help someone run, and it isn't uncommon for it to have zero bids at 100% due to the smaller size and 10% reward cap. It also has a min_age of 20 minutes, fairly typical of bots these days.
There is a scenario that may happen where a user submits a post that is 19 or fewer minutes old, and the bot currently has no bids and is at or near 100%.
The bid will be lost in limbo "next round queue" even when the post hits 20 minutes old due to the fact no further checks are made until another bid comes in. It will then execute that bid and then push the post from the next round to current round.
While this is a rare edge case it's something to think about. Not really critical and may never need to be fixed but mentioning it so I can get it off my mental plate and put it somewhere.
The text was updated successfully, but these errors were encountered:
I ran into an edge case that might be a simple fix if you have a few minutes you are mad at. It's not a critical issue, but I will leave it here anyway.
I have a smaller bot I help someone run, and it isn't uncommon for it to have zero bids at 100% due to the smaller size and 10% reward cap. It also has a min_age of 20 minutes, fairly typical of bots these days.
There is a scenario that may happen where a user submits a post that is 19 or fewer minutes old, and the bot currently has no bids and is at or near 100%.
The bid will be lost in limbo "next round queue" even when the post hits 20 minutes old due to the fact no further checks are made until another bid comes in. It will then execute that bid and then push the post from the next round to current round.
While this is a rare edge case it's something to think about. Not really critical and may never need to be fixed but mentioning it so I can get it off my mental plate and put it somewhere.
The text was updated successfully, but these errors were encountered: