Open pcarn opened 7 months ago
Hey @pcarn, are you still running into this issue after updating to the latest commit on the develop branch? #274 was just merged which did change how this was handled (a side effect) so that may have helped fix this issue.
I'll try and see if it happens again. It's intermittent so hard to tell sometimes.
Right now it's hard to test because I get a lot of Encountered a Too Many Requests error while logging in. Skipping reservation retrieval
errors, even when I'm running it for the first time in several days.
Right now it's hard to test because I get a lot of Encountered a Too Many Requests error while logging in. Skipping reservation retrieval errors
See #277. The develop image should significantly help evading the Too Many Requests error.
It's not looking any better for me, on the current develop branch.
I have also run into this issue. If you start and stop the Docker container a couple of times, the request will exceed the allowed limits. It seems that SW is rate-limiting requests. @jdholtz I reverted back to js_click because after changing to click, this error seemed to happen more often.
@pcarn and @ne0ark can you try this
Docker: docker pull dmytrokoren/auto-southwest-check-in:alpha-proxy Local: dmytrokoren/auto-southwest-check-in : modified_webdriver_and_updated_requirements
@pcarn and @ne0ark can you try this
Docker: docker pull dmytrokoren/auto-southwest-check-in:alpha-proxy Local: dmytrokoren/auto-southwest-check-in : modified_webdriver_and_updated_requirements
Yes, I have been using modified_webdriver_and_updated_requirements on docker, and it works great!
It's been a long time since posting, but I thought I'd add something:
Although it doesn't affect anything, but seems to be happening is the following error: Notice: Webdriver time out during reservation retrieval for XXXXX. Skipping reservation retrieval until next interval.
What I've noticed, although I haven't been able to confirm without editing the code is that for the lines that I indicated check_fares false it would happen on the subsequent check? The initial run was good.
It's been a long time since posting, but I thought I'd add something:
Although it doesn't affect anything, but seems to be happening is the following error: Notice: Webdriver time out during reservation retrieval for XXXXX. Skipping reservation retrieval until next interval.
What I've noticed, although I haven't been able to confirm without editing the code is that for the lines that I indicated check_fares false it would happen on the subsequent check? The initial run was good.
@babehboi
Try this (this should resolve your issue, have been running this for two days with 4hrs interval, no errors)
Docker: docker pull dmytrokoren/auto-southwest-check-in:alpha-window-server Local: dmytrokoren/auto-southwest-check-in : modified_webdriver_and_updated_requirements
I'll give it a try. I'm running the alpha-proxy while on unraid.
Still got it once upon initial start-up with [alpha-window-server]
I'll give it a try. I'm running the alpha-proxy while on unraid.
Still got it once upon initial start-up with [alpha-window-server]
alpha-proxy is outdated.
alpha-window-server you will get either once on initial or second refresh... after that I did not get any errors.
@pcarn @ne0ark @babehboi
Give this image a try:
Docker: docker pull dmytrokoren/auto-southwest-check-in:alpha-legacy-windock
@pcarn @ne0ark @babehboi
Give this image a try:
Docker:
docker pull dmytrokoren/auto-southwest-check-in:alpha-legacy-windock
Thanks. I've been testing this one the past couple of days. It seems to be stable and haven't had that issue in a while
@pcarn @ne0ark @babehboi
Give this image a try:
Docker:
docker pull dmytrokoren/auto-southwest-check-in:alpha-legacy-windock
Thanks. I've been testing this one the past couple of days. It seems to be stable and haven't had that issue in a while
Thanks I'll commit the code soon with these changes
Version
Auto-Southwest Check-In v7.3 (develop branch)
Browser Version
Version 122.0.6261.129 (Official Build) (arm64)
Description
Continuing thread from https://github.com/jdholtz/auto-southwest-check-in/issues/237
Sometimes the URL to set headers is not called, and it gets stuck on
Waiting for headers_set to be set
This commit was added to help, but I still had a flight fail to check-in because it was stuck waiting for headers_set to be set.
If I can get it to happen again, I'll add logs again of what URLs are getting called.
To Reproduce
Not sure, it's intermittent. I have a user and password in my config file. It usually works fine, but sometimes will get stuck. It got stuck on an actual flight check-in the last time I tried.
Expected Behavior
It works normally.
Relevant logs and program output