Attempting to install pytest under Python 2.7.15 and pipenv==2018.11.14 fails to complete with a claimed hash mismatch #3289
Comments
|
Is the build running on windows? If the posix style paths are anything to go by, the resolver is correct to skip the That would be |
techalchemy
added
Status: Needs More Information
|
Negative, the build is running on Docker with the For clarity, the only reason I even brought up the As per your request, I reran the CI build, substituting for Output from $ pipenv --supportPipenv version: Pipenv location: Python location: Python installations found:
PEP 508 Information: System environment variables:
Pipenv–specific environment variables:
Debug–specific environment variables:
Contents of [[source]]
verify_ssl = true
url = "https://pypi.python.org/simple"
name = "pypi"
[packages]
pytest = "*"
[dev-packages]
The failure mode looks to be the same, with pipenv expecting the |
|
Wow. This one is a head scratcher. Thanks for the build logs, that saved a lot of pointless back and forth. I’ll just make an alpine container and see what I can do |
techalchemy
added
Type: Bug 🐛
- Clean up more unused code - Fixes #3289 Signed-off-by: Dan Ryan <[email protected]>
|
That was a fun one! I think i got it sorted out, sorry for the trouble! |
Issue description
Attempting to install
pytestunder Python 2.7.15 andpipenv==2018.11.14fails to complete with a claimed hash mismatch.Expected result
pytestshould successfully install, as it did underpipenv==2018.10.13(build log: https://gitlab.com/kfkitsune/pyHIBP/-/jobs/124421196 ).Actual result
Full verbose output of a minimized test scenario can be found in the following build log, testing only the issue at hand: https://gitlab.com/kfkitsune/pyHIBP/-/jobs/124421197
Steps to replicate
pipenv==2018.11.14.Pipfilewith the following:pipenv --verbose install --dev$ pipenv --support
Pipenv version:
'2018.11.14'Pipenv location:
'/usr/lib/python2.7/site-packages/pipenv'Python location:
'/usr/bin/python2'Python installations found:
2.7.15:/usr/bin/python2.7PEP 508 Information:
System environment variables:
CI_COMMIT_BEFORE_SHACI_CONFIG_PATHCI_PROJECT_NAMESPACECI_BUILD_REF_SLUGCI_SERVER_VERSION_PATCHCI_SERVER_NAMECI_PIPELINE_URLCI_PROJECT_PATH_SLUGCI_COMMIT_MESSAGECI_COMMIT_REF_SLUGCI_PROJECT_VISIBILITYCI_REGISTRY_IMAGECI_COMMIT_REF_NAMECI_COMMIT_SHAPATHHOMECI_REGISTRY_PASSWORDCI_REPOSITORY_URLGITLAB_USER_EMAILCI_DISPOSABLE_ENVIRONMENTCI_RUNNER_IDCI_COMMIT_TITLEGITLAB_CICI_SERVER_TLS_CA_FILECI_RUNNER_EXECUTABLE_ARCHCI_RUNNER_REVISIONSHLVLCI_BUILD_BEFORE_SHACI_BUILD_REF_NAMEGITLAB_USER_NAMECI_BUILD_IDPYTHONFINDER_IGNORE_UNSUPPORTEDCI_RUNNER_VERSIONGITLAB_USER_LOGINCI_PROJECT_PATHDOCKER_DRIVERCI_PROJECT_URLCI_JOB_STAGECI_PROJECT_DIRCI_BUILD_STAGECIGITLAB_USER_IDCI_BUILD_REFCI_REGISTRY_USERCI_SERVER_VERSIONCI_JOB_NAMECI_BUILD_TOKENCI_PROJECT_NAMECI_RUNNER_TAGSCI_COMMIT_DESCRIPTIONPYTHONDONTWRITEBYTECODECI_REGISTRYPIP_PYTHON_PATHCI_JOB_TOKENCI_PROJECT_IDCI_PIPELINE_SOURCECI_SERVER_VERSION_MAJORCI_PIPELINE_IDCI_SERVER_VERSION_MINORCI_SERVER_REVISIONPIP_DISABLE_PIP_VERSION_CHECKOLDPWDHOSTNAMECI_JOB_URLCI_NODE_TOTALPIPENV_CACHE_DIRCI_BUILD_NAMEPIP_CACHE_DIRPWDCI_JOB_IDPIP_SHIMS_BASE_MODULECI_SERVERCI_PIPELINE_IIDCI_RUNNER_DESCRIPTIONGITLAB_FEATURESFF_K8S_USE_ENTRYPOINT_OVER_COMMANDPipenv–specific environment variables:
PIPENV_CACHE_DIR:/builds/kfkitsune/pyHIBP/.cacheDebug–specific environment variables:
PATH:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/binPWD:/builds/kfkitsune/pyHIBPContents of
Pipfile('/builds/kfkitsune/pyHIBP/Pipfile'):Observation
I did take the initiative to compare the SHA-256 value of scandir==1.9.0 as it is on PyPI, and the SHA-256 hash of the file downloaded locally matches that provided by the SHA-256 link on the download page. So I believe it is reasonable to state that the file itself is not corrupt.
However, I did notice that pipenv is claiming that it is expecting
f5c71e29b4e2af7ccdc03a020c626ede51da471173b4a6ad1e904f2b2e04b4bdas the SHA-256 hash. Looking at the verbose scan log, I do see the following:So from the above, we can see that the source tarball is selected for download, and that the claimed SHA-256 hash for the tarball is
44975e209c4827fc18a3486f257154d34ec6eaec0f90fef0cca1caa482db7064, which is what pipenv calculated. However, it was expectingf5c71e29b4e2af7ccdc03a020c626ede51da471173b4a6ad1e904f2b2e04b4bd, which corresponds to the filescandir-1.9.0-cp27-cp27m-win32.whl. As such, while I cannot speak definitively as I have not dug into the source, what I believe is happening is that pipenv incorrectly selected the hash to compare, while using the correct file for calculation (such as, select the firstscandir==1.9.0file link, and use that SHA hash as the expected hash). Again, I don't know if this is actually what is happening, but based on the way the error presents itself, that is my best speculation.The text was updated successfully, but these errors were encountered: