Open paboum opened 6 months ago
503 errors generally mean that Civitai is having issues. There's not really a whole lot I can do on this side except retry until it's working again
How about a user-configurable number of retries, delay or...
For each model, store the last successful check time. If it was less than, say, 15 minutes ago, don't retry updating this one as clearly it only wastes Civitai's resources. This way, when I rerun update, it will only retry the failed ones. User parameter "only download updates for elements older than ___ minutes" would be nice too.
Something akin to that is planned, but it will have to wait until after the holidays
503 errors generally mean that Civitai is having issues. There's not really a whole lot I can do on this side except retry until it's working again
I would suggest adding an option to skip it and continuing on with the next one rather than killing the entire scan simply because retrieving data for a single model failed. Logging the failed models to a text file and adding a "rescan failed models" button would be a nice extra.
If you scan a bigger library, 503 or 401 should lead to stop or as you said at least pause the scan, since civit ai is signaling an overall error or authentication issue. You could always press scan again (in case civit ai is having technical problems like a 503 it will stop nonetheless again). For other HTTP Error which more often signal problems with a single answer/dataset related to the model an automatic resume usually makes sense e.g. model not found in civit.ai.
Scanning should no longer fail due to network issues. If it is still failing, please let me know
Getting this while trying to rescan my checkpoints. Version
203cd5a106fb143b51699e0a7d8e8c28a24442a6
. Need to scan again and again until it succeeds.