Support executable wrappers in `uv_toolchain`
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 3/5
- Tiempo estimado
- 1-2 días
- Aptitud para principiantes
- 45/100
- Tipo de issue
- Nueva funcionalidad
- Claridad
- Bien especificado
- Estado de actividad
- Activo
- Stack tecnológico
- python
- Área
- build-system, tooling
Línea de trabajo
The issue points to uv_toolchain.bzl and lock.bzl. Start by reading those files to understand how the uv executable is currently handled. Look for the uv_toolchain rule definition and the lock rule's action generation. The goal is to modify the toolchain to accept wrappers with multiple outputs and ensure runfiles are preserved. Check how the downloaded uv binary is exposed and how runfiles are collected in Bazel actions. A test involving a wrapper script with credentials would verify the changes.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
🚀 feature request
Relevant Rules
uv_toolchain and lock.
Description
I want to use a custom uv wrapper with the lock rule. In my case, the wrapper would obtain credentials and set index authentication variables before calling the pinned uv binary.
There are a couple of issues right now. First, uv_toolchain rejects executable targets with multiple output files. Second, lock forwards the executable without preserving its runfiles, which limits wrappers that depend on runtime files or symlinks.
Describe the solution you'd like
Allow uv_toolchain to accept executable wrappers with multiple output files. Preserve their runfiles, including ordinary symlinks and root symlinks, in both lock build actions and .run targets.
Export the downloaded uv binary with public visibility so wrappers can declare it as a runtime dependency.
I'll open a PR for this in a bit.
Describe alternatives you've considered
Patching rules_python.
- Lenguaje dominante
- Starlark
- Estrellas
- 690
- Forks
- 722
- Merge medio
- 1 d 55 min
- PR fusionados (30 d)
- 38
Guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de bazel-contrib/rules_python
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 70/100
bazel-contrib/rules_python#4179 ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
bazel-contrib/rules_python#4164 · 1 comentario ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
bazel-contrib/rules_python#3821 ·
-
Release 2.4.0 Abiertotype: release
Dificultad 4/5 3-5 días Aptitud para principiantes 25/100
bazel-contrib/rules_python#4175 · 3 comentarios ·
-
Release 2.3.4 Abiertotype: release
Dificultad 2/5 1-3 horas Aptitud para principiantes 35/100
bazel-contrib/rules_python#4173 · 2 comentarios ·
Todos los issues de bazel-contrib/rules_python
Issues similares
-
Dificultad 1/5 Menos de una hora Aptitud para principiantes 85/100
-
CS0162 "Unreachable code detected" warning from a MSBuildTemp .tmp file in every game project Abiertobug
Dificultad 1/5 Menos de una hora Aptitud para principiantes 90/100
-
area:engineering priority:p2 type:bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
jejjohnson/pyrox#234 ·
-
good first issue
Dificultad 1/5 Menos de una hora Aptitud para principiantes 90/100
-
good first issue
Dificultad 1/5 Menos de una hora Aptitud para principiantes 85/100
ros2/ros2_tracing#266 · 1 comentario ·