-
Notifications
You must be signed in to change notification settings - Fork 30
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
exits with "no such table" #64
Comments
What did your pacoloco.yaml contain? I cannot figure out what happened otherwise. |
I did previously update once through pacoloco successfully, some files exist in |
Ok, I see what happened. The prefetching routine got invoked with no saved mirrors. Could you please check that you had no entries in mirror_dbs? |
Ok, it is probably ok to fail in this situation, it shouldn't do a fatal failure. Updated to do a soft failure (aka, just end the prefetching). |
it's currently not empty:
i set the prefetch cron to just now to test with your branch plus #66 and it succeeded. I'll reopen should I notice it failing again. |
Do not throw fatal error on failed prefetch. It may happen in a very early setup if prefetch is called with no packages upstream and it should be ok. Fixes anatol#64
Do not throw fatal error on failed prefetch. It may happen in a very early setup if prefetch is called with no packages upstream and it should be ok. Fixes #64
i'm running with docker compose.
tonight at the scheduled prefetch time, pacoloco exited with code 1.
this is the end of the log:
The text was updated successfully, but these errors were encountered: