mirror of
https://github.com/User0332/rewards-farmer.git
synced 2026-09-16 01:31:36 +00:00
keep one account's failure from ending a batched run
Only SessionNotCreatedException was isolated. Every other way an account can fail reached main() and took the accounts after it with them: a driver that will not start for another reason, an unwritable profile directory, the first page not loading, the browser dying mid-run, or quit() raising because it was already gone. With REWARDS_ACCOUNTS=one,two,three and the middle one failing, three never ran and main() exited on a traceback instead of an exit code. Catch it around run_account, report it the way a failed task is reported, and carry on. KeyboardInterrupt is left alone so Ctrl-C still stops the run. The quit() in run_account is guarded too, so a tidy-up that raises no longer hides the failure it was tidying up after.
This commit is contained in:
@@ -80,7 +80,7 @@ Each is signed in once by hand, the same way as the single profile, using its ow
|
||||
msedge --user-data-dir="<repo>\data-dir\personal" --profile-directory=Default https://rewards.bing.com
|
||||
```
|
||||
|
||||
They run one after another, and a profile that fails to start is reported and skipped rather than ending the run. Leave `REWARDS_ACCOUNTS` unset and everything behaves exactly as before, using the single profile in `data-dir`.
|
||||
They run one after another, and an account that fails is reported and skipped rather than ending the run, whether it fails to start or dies partway through. Leave `REWARDS_ACCOUNTS` unset and everything behaves exactly as before, using the single profile in `data-dir`.
|
||||
|
||||
# Docker
|
||||
|
||||
|
||||
Reference in New Issue
Block a user