eclipse-score / eclipse-score/communication
Bug: Compilation with rules_python version 2+ is broken
- Dominant language
- C++
- Stars
- 62
- Forks
- 97
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 72
Description
### Description
Compilation with rules_python version 2+ is broken
### Error Occurrence Rate
Reproducible
### How to reproduce
Add `bazel_dep(name = "rules_python", version = "2.0.3")` to `module_integration_test/MODULE.bazel`.
Then run: `cd module_integration_test && bazel build //...`
### Supporting Information
Build error
```sh
bazel build //...
ERROR: /home/q463998/github.com/communication/module_integration_test/BUILD:15:10: While resolving toolchains for target //:example (7d303b4): invalid registered toolchain '//bazel/rules/rules_score:sphinx_default_toolchain': error loading package '@@score_tooling+//bazel/rules/rules_score': at /home/q463998/.cache/bazel/_bazel_q463998/43549a165cb68314752110595e3c4d6d/external/score_tooling+/bazel/rules/rules_score/rules_score.bzl:65:5: at /home/q463998/.cache/bazel/_bazel_q463998/43549a165cb68314752110595e3c4d6d/external/score_tooling+/bazel/rules/rules_score/private/sphinx_module.bzl:18:6: Label '@@rules_python+//sphinxdocs/private:sphinx_docs_library_info.bzl' is invalid because 'sphinxdocs/private' is not a package; perhaps you meant to put the colon here: '@@rules_python+//:sphinxdocs/private/sphinx_docs_library_info.bzl'?
ERROR: Analysis of target '//:example' failed; build aborted
```
### Classification
major
### Affected Version
0.5
### Expected Closure Version
1.0
### Category
- [ ] Safety Related
- [ ] Security Related
Contributor guide
Research direction
Start by updating module_integration_test/MODULE.bazel with rules_python 2.0.3 and run `cd module_integration_test && bazel build //...` to reproduce the toolchain error. Inspect the referenced BUILD target and rules_score error locations in the build output. Done means the module integration build completes successfully with rules_python version 2+.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100