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
As the title, when the timer of the bet is almost done the bot can't place a bet and return an error of EVENT_NOT_ACTIVE but in the settings the "make_predictions" option is set to True.
Steps to reproduce
Set the bot via docker compose and start it up.
Wait for a streamer to place a bet and see that it's not working.
Expected behavior
I expect the bot to place the bet when the timer is almost endend as the setting says.
Operating system
Debian GNU/Linux 12 (bookworm)
Python version
3.11.2
Miner version
1.9.7
Other relevant software versions
No response
Logs
I KNOW that the prompt says "post the log on gist" but i tried EVERYTHING and gist was not accepting my entire log file, always returning an error (I think that is due to the weight of 41.6mb of the file and i also tried to copy-paste all of it).
Describe the bug
As the title, when the timer of the bet is almost done the bot can't place a bet and return an error of EVENT_NOT_ACTIVE but in the settings the "make_predictions" option is set to True.
Steps to reproduce
Set the bot via docker compose and start it up.
Wait for a streamer to place a bet and see that it's not working.
Expected behavior
I expect the bot to place the bet when the timer is almost endend as the setting says.
Operating system
Debian GNU/Linux 12 (bookworm)
Python version
3.11.2
Miner version
1.9.7
Other relevant software versions
No response
Logs
I KNOW that the prompt says "post the log on gist" but i tried EVERYTHING and gist was not accepting my entire log file, always returning an error (I think that is due to the weight of 41.6mb of the file and i also tried to copy-paste all of it).
https://we.tl/t-okJxqNzSBJ
https://gist.github.com/Elmagenta/db90f3e55fbeb573d66f62d8ac84086a
Additional context
The error of "EVENT_NOT_ACTIVE" is at 15:23:43
The text was updated successfully, but these errors were encountered: