RuntimeWarning: coroutine 'AddonManager.handle_lifecycle' was never awaited

[jdholtz]

RuntimeWarning: coroutine 'AddonManager.handle_lifecycle' was never awaited

[jdholtz]

Thanks for reporting this issue. Can you post the script's logs so I can get a better idea of when exactly this happens?

[himnim]

Here's a screenshot of my log. I started the container at 03:15 with 1h login intervals for 2 accounts as defined in config. Since the error occurred at 17:15:10, I assume it was triggered by an attempted login at the scheduled interval.

[jdholtz]

Thanks for sending that. Can you send the actual log file though (it doesn’t contain sensitive information)? asyncio is reporting the issue, but this script never directly uses asyncio, so I am guessing it is a problem with a dependency. The logs will verify exactly when it happens (at what point of the login attempt) so I know how to look into this further.

[himnim]

How would I grab those for you? I see in the troubleshooting section they're stored in logs/auto-southwest-check-in.log, but I don't see that anywhere as I'm running in Docker on Synology. I assume I can pull them by issuing a command to the container?

[himnim]

OK, I managed to figure it out - taking a quick glance myself, I don't see the error at the timestamp in these logs. 2 things I noticed though (may be unrelated and/or I can open a new bug report if necessary)

auto-southwest-check-in.log

I have 2 accounts monitored with this, 1 account has 2 flights reserved and the other account had 3 flights reserved, but then I cancelled 1 on 5/8. I assume Process-1 is for 1 account and Process-2 is for the other account. In these logs, Process-1 ends up disappearing on 5/10. Additionally, Process 2 states "Currently have 3 flights scheduled" even though it should only be 2 at that point.

[jdholtz]

I appreciate you attaching the logs. Process-1 appears to be the one that failed, but the exception was never logged (I don't have it set up for that). It failed when starting the webdriver so I looked around for Selenium issues relating to it and came across selenium-wire #238 and selenium-wire #361. Both times the issue seems to have been a very rare occurrence.

There seems to be many issues reported relating to starting the webdriver (see #90). I will implement a better algorithm to start the driver to hopefully fix these rare and random issues.

As for the cancelled flight, I have plans to handle this scenario (it shouldn't be hard to implement). However, it isn't high on the priority list right now as it won't actually hurt the execution of the script. It will obviously send a failed check-in notification, but this can be safely ignored. Feel free to open an issue on it though

[jdholtz]

I added more resistance to random errors like this while initializing the webdriver. Let me know if you run into any more issues related to this.