Fix issue with installing dependencies with extras & hashes

[di]

Adds a test for #9644.

Fixes #9644.

[uranusjr]

Re-initialiting CI

[uranusjr]

@di How about marking the test as xfail(strict=True)? That way I can merge this into main and the acual fix can be submitted separately. I might have some time to spend on this as well.

[di]

Could a maintainer or contributor point me in the right direction here? Is this an issue in the resolver itself, outside the resolver, etc? Any leads would be helpful for me figure out where to start with fixing this.

[uranusjr]

This is not strictly a resolver issue, but you’ll need to make changes to the resolver implementation so user-specified hashes and extras pass through it into the hash-checking component to satisfy the check. I believe the exception is raised during prepare_linked_requirement() (someone need to verify this), which is called when an _InstallRequirementBackedCandidate is instantiated. But the underlying InstallRequirement that backs the candidate does not currently have the correct hashes populated, so when prepare_linked_requirement() is called, the InstallRequirement passed into it fails the hash check.

So to fix the issue, you’ll need to find out where the user-specified hashes are dropped and not correctly passed to the InstallRequirement backing the _InstallRequirementBackedCandidate (it has two subclasses, but only LinkCandidate is relevant since EditableCandidate cannot have hashes), and fix that to correctly pass on the hash values. I would probably start with somewhere in factory.py, that’s where the hashes are collected in the current implementation.

[di]

Hey, look at that, the failing test is now passing 🙂