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

debugpy wheel file validation fails #83

Closed
kitsuyui opened this issue Mar 22, 2023 · 1 comment · Fixed by #93
Closed

debugpy wheel file validation fails #83

kitsuyui opened this issue Mar 22, 2023 · 1 comment · Fixed by #93

Comments

@kitsuyui
Copy link
Owner

kitsuyui commented Mar 22, 2023

The following problem is occurring, and CI is failing on GitHub Actions.

  _WheelFileValidationError

  ["In /home/runner/.cache/pypoetry/artifacts/XXX/debugpy-1.6.6-py2.py3-none-any.whl, hash / size of debugpy/_vendored/pydevd/_pydevd_bundle/pydevd_cython.cp39-win_amd64.pyd didn't match RECORD", "In /home/runner/.cache/pypoetry/artifacts/XXX/debugpy-1.6.6-py2.py3-none-any.whl, hash / size of debugpy/_vendored/pydevd/_pydevd_frame_eval/pydevd_frame_evaluator.cp39-win_amd64.pyd didn't match RECORD", "In /home/runner/.cache/pypoetry/artifacts/XXX/debugpy-1.6.6-py2.py3-none-any.whl, hash / size of debugpy/_vendored/pydevd/pydevd_attach_to_process/attach_amd64.dll didn't match RECORD", "In /home/runner/.cache/pypoetry/artifacts/XXX/debugpy-1.6.6-py2.py3-none-any.whl, hash / size of debugpy/_vendored/pydevd/pydevd_attach_to_process/attach_x86.dll didn't match RECORD", "In /home/runner/.cache/pypoetry/artifacts/XXX/debugpy-1.6.6-py2.py3-none-any.whl, hash / size of debugpy/_vendored/pydevd/pydevd_attach_to_process/inject_dll_amd64.exe didn't match RECORD", "In /home/runner/.cache/pypoetry/artifacts/XXX/debugpy-1.6.6-py2.py3-none-any.whl, hash / size of debugpy/_vendored/pydevd/pydevd_attach_to_process/inject_dll_x86.exe didn't match RECORD", "In /home/runner/.cache/pypoetry/artifacts/XXX/debugpy-1.6.6-py2.py3-none-any.whl, hash / size of debugpy/_vendored/pydevd/pydevd_attach_to_process/run_code_on_dllmain_amd64.dll didn't match RECORD", "In /home/runner/.cache/pypoetry/artifacts/XXX/debugpy-1.6.6-py2.py3-none-any.whl, hash / size of debugpy/_vendored/pydevd/pydevd_attach_to_process/run_code_on_dllmain_x86.dll didn't match RECORD"]

  at /opt/hostedtoolcache/Python/3.11.2/x64/lib/python3.11/site-packages/installer/sources.py:289 in validate_record
      285│                         f"In {self._zipfile.filename}, hash / size of {item.filename} didn't match RECORD"
      286│                     )
      287│ 
      288│         if issues:
    → 289│             raise _WheelFileValidationError(issues)
      290│ 
      291│     def get_contents(self) -> Iterator[WheelContentElement]:
      292│         """Sequential access to all contents of the wheel (including dist-info files).
      293│ 

Previously, the build succeeded on 3.11. At least #77 succeeded.
From the error message, the following reasons can be considered.

  • Incompatibility due to operational mistakes
  • Spontaneous damage of binary (defective disk or cosmic ray damage to memory)
  • Binary replacement by malicious existence

In my experience, I think that operational mistakes are most likely to cause incompatibility.
A workaround of poetry config installer.modern-installation false is suggested in the comment, but this is not a fundamental solution.
In any case, this problem should be solved by waiting for a new version of debugpy to be released, I think.
Since this program does not require Windows, it may be worth considering removing Windows from the target platform if it takes too long.

Links

microsoft/debugpy#1246

@kitsuyui
Copy link
Owner Author

kitsuyui commented Mar 22, 2023

I noticed python-poetry/poetry#7686 .
This problem is unclear whether it is a problem with poetry or a problem with the package.

kitsuyui added a commit that referenced this issue Mar 27, 2023
The version update has been delayed until the workaround #86 for #83.
Update the version of each package.
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

Successfully merging a pull request may close this issue.

1 participant