You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
efficientvit @ git+https://github.com/mit-han-lab/efficientvit.git@4cc0a75fb5225f2986fa5733f5bfe7c8b9ad4813
# via -r requirements.in
tinyneuralnetwork @ git+https://github.com/alibaba/TinyNeuralNetwork.git@c9d0ac571086212b4a62d2bacf6bfe12d92556e1
# via efficientvit
🔥 Exception or Error
ERROR: /home/baxelrod/.cache/bazel/_bazel_baxelrod/223f490fa0c2f2ec38707ddac3dd6272/external/rules_python+/python/private/pypi/extension.bzl:617:20: Traceback (most recent call last):
File "/home/baxelrod/.cache/bazel/_bazel_baxelrod/223f490fa0c2f2ec38707ddac3dd6272/external/rules_python+/python/private/pypi/extension.bzl", line 617, column 20, in _pip_impl
whl_library(name = name, **args)
Error in repository_rule: invalid user-provided repo name 'pip_u2204_310__TinyNeuralNetwork_git@c9d0ac571086212b4a62d2bacf6bfe12d92556e1': valid names may contain only A-Z, a-z, 0-9, '-', '_', '.', and must start with a letter
ERROR: error evaluating module extension @@rules_python+//python/extensions:pip.bzl%pip
it works with rules_python 1.2.0 but fails with 1.3.0 and 14.0-rc2 (bcr)
Error in repository_rule: invalid user-provided repo name 'pip_311_torch_2_6_0%2bcpu_cp311_cp311_sdist_5b6ae523': valid names may contain only A-Z, a-z, 0-9, '-', '_', '.', and must start with a letter
Activity
neyo8826 commentedon Apr 28, 2025
the same happens with
bazel 8.2.1
it works with rules_python 1.2.0 but fails with 1.3.0 and 14.0-rc2 (bcr)
aignas commentedon Apr 29, 2025
This is probably still an issue with 1.4.0-rc3.
fix(pypi): handle more URL patterns for requirement sources
aignas commentedon Apr 29, 2025
Could you please check if the PR #2843 helps with the issues you are both seeing?
fix(pypi): handle more URL patterns for requirement sources (#2843)
fix(pypi): handle more URL patterns for requirement sources (#2843)
baxelrod-bdai commentedon Apr 29, 2025
I still get the same error with
1.4.0-rc3baxelrod-bdai commentedon Apr 29, 2025
Fixed in
1.4.0-rc4