Version
v7.5 (develop branch)
Browser Version
N/A
Description
With the merge of #274 on the develop branch, 403 and 429 errors are being handled much better (or not even seen). I want to consolidate the #201 and #230 threads into one. Using the thread below, people can report if they are or aren't seeing these errors as well as the environment they're using (Docker, laptop, server, etc.) and how many accounts/reservations are being monitored.
To Reproduce
- Run either the Docker image or the local Python installation
- See if any requests fail (using either the
--verbose flag or the log files which will have more information on any failed attempts)
Expected Behavior
It is not expected that you never see 403 or 429 errors again. However, with the recent changes you should still eventually have successful attempts at logging in, scheduling check ins, fare checking, and checking in. The goal is to have no attempts too many times to the point they are not retried (the corresponding log message: Failed to make request after ... attempts: ...)
Relevant logs and program output
No response
Additional context
For the most part, only logs like the following are helpful.
Request error on attempt ... Sleeping for 1.98 seconds until next attempt
Pasting all logs are fine, but please use a collapsed section in order to not clutter the main thread.
To get the latest changes, you can either use Docker or the develop branch locally.
Docker: docker pull jdholtz/auto-southwest-check-in:develop
Local: git pull && git checkout develop
Version
v7.5 (develop branch)
Browser Version
N/A
Description
With the merge of #274 on the
developbranch, 403 and 429 errors are being handled much better (or not even seen). I want to consolidate the #201 and #230 threads into one. Using the thread below, people can report if they are or aren't seeing these errors as well as the environment they're using (Docker, laptop, server, etc.) and how many accounts/reservations are being monitored.To Reproduce
--verboseflag or the log files which will have more information on any failed attempts)Expected Behavior
It is not expected that you never see 403 or 429 errors again. However, with the recent changes you should still eventually have successful attempts at logging in, scheduling check ins, fare checking, and checking in. The goal is to have no attempts too many times to the point they are not retried (the corresponding log message:
Failed to make request after ... attempts: ...)Relevant logs and program output
No response
Additional context
For the most part, only logs like the following are helpful.
Request error on attempt ... Sleeping for 1.98 seconds until next attemptPasting all logs are fine, but please use a collapsed section in order to not clutter the main thread.
To get the latest changes, you can either use Docker or the
developbranch locally.Docker:
docker pull jdholtz/auto-southwest-check-in:developLocal:
git pull && git checkout develop