Open dz1419 opened 8 months ago
As previously noted I'm pretty busy atm, but I've taken a quick look at this bug. The network error occurs on line 366
in api/resy/api.go
. The status code returned is 500. For anyone whose looked in the source files, this occurs at the config
step of the reserve api operation. I checked to make sure the api key in the codebase is still valid and tried adding a user agent header. These didn't fix the issue. Given that the previous operations succeeded but this one fails, and the other investigating I've done, I see two possible issues. 1) The API for the config step has changed, I'll perform some analysis on this the next free moment I have. 2) Resy has increased their use of Captcha, and this is blocking the bot. This is way more probable, since the previous network calls succeed, so it would be weird for this one step to change APIs, and a very fast analysis using firefox network tab showed that that headers are still all pretty much the same :( . In this first case, maybe we can submit a patch, but the second requires a lot of work to get around, so I'd say the bot will be down for at a minimum three more weeks and at an estimated maximum a half year. Sorry.
Is there an existing issue for this bug?
Description of the bug
After bot is firing I am getting an unknown network error. I am using this version 60e88dd
Steps to reproduce
I am just running a rats command and after the time hits for the request date and I run the list command I am getting an unknown network error. I have tested with a few different venue IDs. rats -v XXXX-resD 2024:03:13 -resT 20:00 -ps 2 -reqD 2024:03:04:13:10
System Specs
Windows - Git Bash
Additional Context
No response