Closed shetaron closed 7 months ago
The bot is stuck. I shouldn't have assumed you would remember that it's always me that puts in this ticket.
Thanks for the heads up I'll fix in a few hours :)
guess who's back baby
Back again for my bi weekly bot kick
Thanks will kick! Really need to try and find a more aggressive keep alive. Not sure why twitch kicks me off of the IRC
Good morning. Bot needs another kick.
Thanks for always doing this
Apologies for the inconveniences! Out at a conference will be able to address Sunday night / Monday!
Forgot to comment service should be up and running. Gave it a kick a few days ago.
Commenting again to say the bot needs another kick today
kicked
Note to self. I believe keep-alive code for the server is actually really adequate. 🦍 brain just put 2+2 together and if I ever watch a SaltyBet stream I think Twitch dislikes the same user being logged in from multiple sources and probably disconnects the client from the IRC.
bump
hi, bot in need of a kick
kicked :)
Bot needs to be woken up
I think it needs a kick. Hasn't worked in a few days.
Oh sorry about that will kick soon! Thank you for letting me know :)
On Thu., Aug. 31, 2023, 4:34 a.m. Stuemke17, @.***> wrote:
I think it needs a kick. Hasn't worked in a few days.
— Reply to this email directly, view it on GitHub https://github.com/FranciscoAT/saltyboy/issues/62#issuecomment-1700600829, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABLUMUW4WBRXYKERG27NO3DXYBEBDANCNFSM6AAAAAAYYILID4 . You are receiving this because you commented.Message ID: @.***>
Omg it's been down since the 12th! Should've told me earlier lol! Thanks for the heads up, should be kicking! :D
Beep boop, bot needs a reboot
kick please :)
Bot is alive, but looks like Waif4u is down SaltyBet side.
On Wed, Nov 29, 2023 at 2:59 PM shetaron @.***> wrote:
kick please :)
— Reply to this email directly, view it on GitHub https://github.com/FranciscoAT/saltyboy/issues/62#issuecomment-1832615256, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABLUMUQ2PEM2YQ6OAJZHOMLYG6H2LAVCNFSM6AAAAAAYYILID6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMZSGYYTKMRVGY . You are receiving this because you commented.Message ID: @.***>
looks like bot is down, keep betting 1$on red and match and overlay not updating.
bot is down again today.
bot is down, kept betting 1 in tournament even though i set to go all in
I believe the bot is down again. Its not betting.
I believe the bot is down again. Its not betting.
Happened to be around. Just looked, still alive. Possible different issue?
Maybe, let me restart my pc. It has been running for awhile lol
That did the trick! Thanks for popping in though!
Oh a possible issue, next time check for query parameters in your URL. It's a known issue, #81
bot is down again, bet 1 even when i set max bet more than that, overlay not showing and problem still persist even after reloging in a few times.
I think it needs a kick, its been sitting on a fight about 10 rounds ago in a tournament
bots down again, stuck on a previous match
Worth noting I was reading through https://docs.python.org/3/howto/sockets.html. Came across an interesting excerpt and potential solution to this issue:
When a
recv
returns 0 bytes, it means the other side has closed (or is in the process of closing) the connection. You will not receive any more data on this connection. Ever. You may be able to send data successfully; ...
A heads up for those of you on this thread. Going to be doing some Big Updates :tm: shortly. You will experience a service disruption. You can follow the release here: https://github.com/FranciscoAT/saltyboy/issues/88. Will notify on that thread once release operations are completed. Please do comment on that issue if you experience any additional issues or weird bugs! :heart:
UPDATE [22-02-2024 18:26 ETC]: Major release changes are complete. Services are looking mostly healthy.
Hi all! I'm finally going to put this issue to rest. I've done some bug fixes and have had some changes deployed for a while in production and have seen successful recovery when the bot goes down. Notable changes are:
Please note the following:
GET /api/current_match_info/
endpoint which means the extension will default back to betting 1 on Red. It should be noted that this only happens roughly 0-2 times a day on average from what I can see. Worst cases tend to be upwards of 4-5 matches a day. So if you notice the bot fail wait until the next match, if it's still not working wait roughly 10-15 before opening an issue.
I'm so sorry