-
Notifications
You must be signed in to change notification settings - Fork 28
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
pipupgrade stuck on Checking... excessive resource usage #105
Comments
Hmm, I'm starting to think this issue is with Python itself, not your script. Although pip-check did manage to update the packages without similar behaviour.. |
same, win10, ran pipupgrade, new laptop so not a resources issue, stuck on checking, "pip3 list --outdated" ran fine and instantly. |
Did you try checking #30? |
Going to close, if you believe this is different from #30 feel free to repoen. |
I need to reopen this. Unfortunately deleting pip's cache didn't work for me. pipupgrade is still hammering the RPi to the point where it's not progressing past "Checking..." Why does it need to fork/run that many instances at the same time? Can it not consolidate, or run a few at a time, or sequentially? |
Reopening |
@sgreadly Did you try decreasing the number of jobs it uses. |
Thanks, didn't notice that option. Yes it does help if i set to -j 1. CPU is still 100% solid, but it does go through pip and pip3 at around ~10-15 minutes for each. I need to fix why it's stopping at pip2 tomorrow then will give it another test. ''' multiprocessing.pool.RemoteTraceback: The above exception was the direct cause of the following exception: Traceback (most recent call last): An error occured while performing the above command. This could be an issue with |
Putting pip2 aside as I don't use it, yea managed to it to work with 1 job and just on pip3. Took ~8 minutes. $ pipupgrade -Vj 1 --pip-path /home/pi/.local/bin/pip3 Thanks! I guess you can close this off. |
@sgreadly You're welcome. |
What's the bug all about?
pipupgrade is stuck on "Checking...".
It seems to need a lot of resources (Mem/CPU), which is not feasible on simpler hardware like the Raspberry Pi Zero WH I'm on. Can't seem to handle its needs :/
What command led to this issue?
Logs
Please paste the logs using
pipupgrade --verbose
The text was updated successfully, but these errors were encountered: