Skip to content

[pull] main from bazel-contrib:main#488

Merged
pull[bot] merged 1 commit into
garymm:mainfrom
bazel-contrib:main
Jan 12, 2026
Merged

[pull] main from bazel-contrib:main#488
pull[bot] merged 1 commit into
garymm:mainfrom
bazel-contrib:main

Conversation

@pull
Copy link
Copy Markdown

@pull pull Bot commented Jan 12, 2026

See Commits and Changes for more details.


Created by pull[bot] (v2.0.0-alpha.4)

Can you help keep this open source service alive? 💖 Please sponsor : )

…is not in root module (#3505)

When: 1) venv_site_packages is on 2) we have a py_binary in a non-root
module (e.g. a tool used in rules), and it uses python deps that result
in usage of runfiles.symlinks, the `ctx.runfile` based symlinks end up
going in the wrong folder (`_main`), while the
`ctx.actions.symlink(...)` files go in the right place. This results in
an invalid `venv` and import errors.

The reason is that `actions.symlinks` always go to the `_main` module,
as [Bazel docs
explain](https://bazel.build/extending/rules#runfiles_symlinks). To send
symlinks to other modules, one needs to use root_symlinks and prefix
them with the right module name.

Fixes: #3503

---------

Co-authored-by: Shayan Hoshyari <hoshyari@adobe.com>
Co-authored-by: Richard Levasseur <rlevasseur@google.com>
@pull pull Bot locked and limited conversation to collaborators Jan 12, 2026
@pull pull Bot added the ⤵️ pull label Jan 12, 2026
@pull pull Bot merged commit f9992f7 into garymm:main Jan 12, 2026
2 checks passed
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant