22.0: `assert len(weights) == expected_node_count AssertionError`
See original GitHub issueDescription
Hi there,
I’m one of the maintainers for Qtile (https://www.github.com/qtile/qtile).
I’ve noticed that our docs (hosted by ReadTheDocs) have begun failing to build.
The error message is:
ERROR: Exception:
Traceback (most recent call last):
File "/home/docs/checkouts/readthedocs.org/user_builds/qtile/envs/3274/lib/python3.7/site-packages/pip/_internal/cli/base_command.py", line 165, in exc_logging_wrapper
status = run_func(*args)
File "/home/docs/checkouts/readthedocs.org/user_builds/qtile/envs/3274/lib/python3.7/site-packages/pip/_internal/cli/req_command.py", line 205, in wrapper
return func(self, options, args)
File "/home/docs/checkouts/readthedocs.org/user_builds/qtile/envs/3274/lib/python3.7/site-packages/pip/_internal/commands/install.py", line 389, in run
to_install = resolver.get_installation_order(requirement_set)
File "/home/docs/checkouts/readthedocs.org/user_builds/qtile/envs/3274/lib/python3.7/site-packages/pip/_internal/resolution/resolvelib/resolver.py", line 190, in get_installation_order
expected_node_count=len(self._result.mapping) + 1,
File "/home/docs/checkouts/readthedocs.org/user_builds/qtile/envs/3274/lib/python3.7/site-packages/pip/_internal/resolution/resolvelib/resolver.py", line 276, in get_topological_weights
assert len(weights) == expected_node_count
AssertionError
The first failure (https://readthedocs.org/projects/qtile/builds/15928125/) was the first build following the release of 22.0.
The most recent failure (https://readthedocs.org/projects/qtile/builds/15931046/) also fails on 22.0.1.
Expected behavior
Documents should build successfully.
I’m not aware of any other changes that would have impacted the building of our docs.
pip version
22.0 and 22.0.1
Python version
3.7
OS
ReadTheDocs docker image - I think is Ubuntu 20.04
How to Reproduce
(Appreciate this isn’t particularly helpful…)
- Submit a PR for Qtile
- Hook starts build of docs
- Build fails
Note: I cannot recreate locally. However, given that the failures started with 22.0 I can only assume it’s caused by that. Unfortunately, I don’t know what the error message means.
Output
No response
Code of Conduct
- I agree to follow the PSF Code of Conduct.
Issue Analytics
- State:
- Created 2 years ago
- Reactions:5
- Comments:18 (13 by maintainers)
Top GitHub Comments
I am able to reproduce the error following these steps with a fresh virtual environment. Here are the steps specifically:
And the requirements file looks like this:
I have not been able to reproduce it using a single install or using download.
I set a breakpoint where the asert statement is and I found:
This issue is closed. If you have a new issue with the latest version of pip (currently 22.0.3) you should report that new issue.