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
Unexpected Error occurs and "generating global index page..." take too many time #1108
Comments
One more thing:
|
You're an inquisitive one ...
When we error, we still log it. Maybe that's the confusion here.
If the mirror you set does not have the file, I'm pretty sure we fall back. I'd have to read the code to be 100%.
I ment, we'd have to change the code to support that option. As in do a PR. That option does not exist today.
Yes, bandersnatch is designed to be eventual consistent. We don't ever expect a perfect run every time. This is the internet after all.
https://bandersnatch.readthedocs.io/en/latest/filtering_configuration.html#prerelease-filtering
Please feel free to submit any updates to documentation if you'd like to help make it more understandable. |
case
The console output logs:
From the logs, we can see that bandersnatch took almost 90 mins to do
generating global index page
even0 packages had changes
. This often happen when the bandersnatch run with error like:After this error happen, bandersnatch will go straight toward to
generating global index page
and then finish the work. However, you need to rerunbandersnatch
for anothergenerating global index page
operation( but I don't know why) to removetodo
file and then can resume to a normal status.questions
So here I have some questions:
stop-on-error=Flase
, but why the bandersnatch still make a stop-like action whenERROR: Error syncing package
download-mirror
, but recently bandersnatch often gives hints like "conducting to next uri" and then download from "https://files.pythonhosted.org", which is much more slower. Why would this happen?The text was updated successfully, but these errors were encountered: