Skip to content
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

long time hang at "pip is looking at multiple versions of chardet" #1721

Closed
elig0n opened this issue Apr 19, 2021 · 5 comments
Closed

long time hang at "pip is looking at multiple versions of chardet" #1721

elig0n opened this issue Apr 19, 2021 · 5 comments

Comments

@elig0n
Copy link
Contributor

elig0n commented Apr 19, 2021

ENVIRONMENT

OS and Version: Linux and Windows
Python Version: 3.9.4
MobSF Version: Git

EXPLANATION OF THE ISSUE

When running setup.bat or setup.sh pip would provide the following message and stop producing output for a long time (hours). I had an instance where after leaving it on for 24 hours I would see it finished.

INFO: pip is looking at multiple versions of chardet to determine which version is compatible with other requirements. This could take a while.
INFO: This is taking longer than usual. You might need to provide the dependency resolver with stricter constraints to reduce runtime. If you want to abort this run, you can press Ctrl + C to do so. To improve how pip performs, tell us what happened here: https://pip.pypa.io/surveys/backtracking

I have noticed this "multiple version looking" happen with other packages as well but chardet seems to be the longest. I hope there is a way to shorten all of this.

@github-actions
Copy link

👋 @elig0n
Issues is only for reporting a bug/feature request. For limited support, questions, and discussions, please join MobSF Slack channel: http://tiny.cc/mobsf
Please include all the requested and relevant information when opening a bug report. Improper reports will be closed without any response.

@elig0n
Copy link
Contributor Author

elig0n commented Apr 19, 2021

Also see: pypa/pip#8713

@ajinabraham
Copy link
Member

Hi @elig0n this is a known issue and our setup scripts are updated to use the legacy resolver for the time being. Please pull the latest master and try running setup again.

@elig0n
Copy link
Contributor Author

elig0n commented Apr 19, 2021

@ajinabraham Are both windows and nix setup scripts updated ?
Can you point to the relevant commits ?

This is also happening for the certifi package.

@ajinabraham
Copy link
Member

pip install --no-cache-dir --use-deprecated=legacy-resolver -r requirements.txt

There is similar change for windows as well. We also have automated cross platform tests running against each commit.
https://github.com/MobSF/Mobile-Security-Framework-MobSF/actions/workflows/mobsf_test.yml

@elig0n elig0n closed this as completed Apr 19, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants