Ability to run multiple instances of the script

[jdholtz]

Ability to run multiple instances of the script

[jdholtz]

This should already be possible by adding multiple accounts/flights to the configuration file. It was added back in #33. Let me know if you are still having issues after trying this.

[jdholtz]

I will close this as this feature has already been added. If you have any further issues with this, this issue can be reopened.

[joshbgosh10592]

Sorry I missed that before opening this issue!
However, after trying this, I entered my flight info and then my SO's flight info and the script is only displaying my flight was found, but no errors. The flight is soon and I don't fly all that much, so I might not be able to test all that much.

[jdholtz]

Could you send the logs of the script for the run that has the error? Also to clarify, does it say your SO’s reservation is not found? Or does it not check for the reservation at all?

[joshbgosh10592]

Sure can! Please see attached (hopefully it works lol). It seems to not even try. After it checks and outputs (scrubbed, of course)
Successfully scheduled the following flights to check in for myFirst myLast:
Flight from CITY1 to CITY2 at 2023-05-99 23:23:23 UTC
auto-southwest-check-in.log

[jdholtz]

Thanks. It appears that it is halting when starting the webdriver. If you leave it long enough (2-3 minutes), does it eventually throw an error or is there nothing at all?

[joshbgosh10592]

No problem, and thank you!
I left it for about 15 minutes and it just stayed there with that same output.
What's even more strange is that I just did it again (after adding notification settings) and this time it only checked her flight and not mine. My reservation information is still above her's, so I'm confused..
auto-southwest-check-in.log

Just to check, this syntax is correct, right?

Edit: I'm on the Dev branch because a previous check-in failed with the 429 error. It looks like every other run throws a chromedriver error saying it's running v112 and requires 113.

I also then reran the script and it haulted on my reservation and not hers this time.
So, every other run throws the chromedriver error, and every successful run alternates between her and my reservation...

[jdholtz]

The configuration file looks correct. Chromedriver will not work if there is a version discrepancy. To solve this, you can either upgrade Chrome or specify the version in the config file.

As for why it might only successfully work for one flight is probably just whichever one uses the driver first.

You can also run this script in Docker for now until we can figure this out.

[joshbgosh10592]

I actually had upgraded Chrome after I got the error the first time from 112 to 113. I just now specified the version in the config file. I no longer get that error, but now it's only trying my reservation and not trying hers.

I'm not able to get Docker up and running before the flight, but that would have been a good idea lol.

nevermind, I'm still getting the chrome error after the script woke up before the check-in.
This also then caused the script to not proceed and check in anyone. The log threw this:
2023-05-05 15:16:06 DEBUG Process-1[flight_retriever]: Sleeping for 86399 seconds
2023-05-05 15:16:09 DEBUG Process-1:1[checkin_handler]: Sleeping until ten minutes before check-in...
2023-05-05 15:39:55 DEBUG Process-1:1[checkin_scheduler]: Refreshing headers for current session
2023-05-05 15:39:55 DEBUG Process-1:1[webdriver]: Starting webdriver for current session

check in was 3:50p EDT (local to VM running script)

[jdholtz]

What operating system are you running this on? You could also try by specifying the chromedriver_path in the configuration. A potential reason it isn’t working is because it is trying to download the latest driver every time so this configuration option would fix it.