failures with autogenerated `_test` when using `pypi.fury.io` and `python_platform`

[baxelrod-bdai]

I'm generating a lock file like this:

pip_compile(
    name = "requirements",
        extra_args = [
            "--quiet",
            "--extra-index-url=https://pypi.fury.io/team-dmm/",
            "--index-strategy=unsafe-best-match",
        ],
    python_platform = "aarch64-manylinux_2_40",
    requirements_in = "requirements.in",
    requirements_txt = "requirements.lock",
)

And I have only this in requirements.in:

pygame

But when I run the _test target, I get this error:

==================== Test output for //:requirements_test:
FAIL: req_test.lock is out-of-date. Run 'bazel run @@//:requirements' to update.
6,66c6,63
< pygame==2.6.1 \
<     --hash=sha256:00827aba089355925902d533f9c41e79a799641f03746c50a374dc5c3362e43d \
<     --hash=sha256:fb6e8d0547f30ddc845f4fd1e33070ef548233ad0dbf21f7ecea768883d1bbdc
---
> pygame==2.6.0 \
>     --hash=sha256:098029d01a46ea4e30620dfb7c28a577070b456c8fc96350dde05f85c0bf51b5 \
>     --hash=sha256:fea019713d0c89dfd5909225aa933010100035d1cd30e6c936e8b6f00529fb80
================================================================================
Target //:requirements_test up-to-date:
  bazel-bin/requirements_test

(A bunch of hashes omitted for brevity)

If I remove either "--extra-index-url=https://pypi.fury.io/team-dmm/", or python_platform = "aarch64-manylinux_2_40", then the lock generation and _test succeed.

https://pypi.fury.io/team-dmm/pygame lists only:

pygame-2.6.0-cp310-cp310-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
pygame-2.6.1-cp310-cp310-manylinux_2_17_x86_64.manylinux2014_x86_64.whl

Using versions:

• Bazel 8.1.1
• rules_uv 0.71.0
• I'm on Linux Ubuntu 22.04, x86_64

[baxelrod-bdai]

If I compare the lock file generated with and without the offending lines, the only difference is the comment at the top with --extra-index-url https://pypi.fury.io/team-dmm/.

for example:

# This file was autogenerated by uv via the following command:
#    bazel run @@//:requirements
--index-url https://pypi.org/simple
--extra-index-url https://pypi.fury.io/team-dmm/

pygame==2.6.1 \
    --hash=sha256:00827aba089355925902d533f9c41e79a799641f03746c50a374dc5c3362e43d \
    --hash=sha256:10e3d2a55f001f6c0a6eb44aa79ea7607091c9352b946692acedb2ac1482f1c9 \
    ...

Is the problem that the _test doesn't know what platform architecture to use?

[markelliot]

I think the issue here is that your input is unconstrained, so the test resolves to the highest available version

[baxelrod-bdai]

I think the issue here is that your input is unconstrained, so the test resolves to the highest available version

That's not it. I have many other unconstrained, or >= constraints in other .in files with no issue. Furthermore, when uv pip compile runs, it takes into account the existing lock file and doesn't upgrade a target if it is currently valid.

This is easy to test:
Assuming you have this in BUILD.bazel

pip_compile(
    name = "generate_requirements_txt",
    requirements_in = "//:requirements.in",
    requirements_txt = "//:requirements.txt",
)

now put something like

pygame == 2.0

in requirements.in. then

bazel run //:generate_requirements_txt
bazel test //:generate_requirements_txt_test --cache_test_results=no

both run fine. the lock file has pygame == 2.0.0 as expected.

now change the requirements.in file to have:

pygame >= 1.0

now

bazel run //:generate_requirements_txt
bazel test //:generate_requirements_txt_test --cache_test_results=no

both succeed. the lock file will still have pygame == 2.0.0.

but now if you

rm requirements.txt
touch requirements.txt
bazel run //:generate_requirements_txt
bazel test //:generate_requirements_txt_test --cache_test_results=no

the lock file will have pygame == 2.6.1`.