Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: py_proto_library: external runfiles #2516

Merged
merged 1 commit into from
Dec 22, 2024

Conversation

tpudlik
Copy link
Contributor

@tpudlik tpudlik commented Dec 20, 2024

Previously, the import path within the runfiles was only correct for the case --legacy_external_runfiles=True (which copied the runfiles into $RUNFILES/<main repo>/external/<external repo>/<path> in addition to $RUNFILES/<external repo>/<path>. This flag was flipped to False in Bazel 8.0.0.

Fixes #2515.

Tested locally against the minimal reproducer in that issue.

@tpudlik tpudlik force-pushed the legacy_external_runfiles branch 3 times, most recently from 5e31d8f to b83c3e6 Compare December 20, 2024 19:21
Previously, the import path within the runfiles was only correct for the
case --legacy_external_runfiles=True (which copied the runfiles into
`$RUNFILES/<main repo>/external/<external repo>/<path>` in addition to
`$RUNFILES/<external repo>/<path>`. This flag was flipped to False in
Bazel 8.0.0.

Fixes bazelbuild#2515.

Added a regression test, and tested locally against the minimal
reproducer in that issue.
@tpudlik tpudlik force-pushed the legacy_external_runfiles branch from b83c3e6 to 929df99 Compare December 20, 2024 20:49
@tpudlik tpudlik marked this pull request as ready for review December 20, 2024 22:19
@aignas aignas added this pull request to the merge queue Dec 22, 2024
Merged via the queue into bazelbuild:main with commit e3c9406 Dec 22, 2024
4 checks passed
copybara-service bot pushed a commit to protocolbuffers/protobuf that referenced this pull request Feb 1, 2025
Previously, the import path within the runfiles was only correct for the case `--legacy_external_runfiles=True` (which copied the runfiles into `$RUNFILES/<main repo>/external/<external repo>/<path>` in addition to `$RUNFILES/<external repo>/<path>`. This flag was flipped to False in Bazel 8.0.0.

This is identical to the change made to rules_python in bazelbuild/rules_python#2516.

Work towards bazelbuild/rules_python#2581.

PiperOrigin-RevId: 721941173
copybara-service bot pushed a commit to protocolbuffers/protobuf that referenced this pull request Feb 1, 2025
Previously, the import path within the runfiles was only correct for the case `--legacy_external_runfiles=True` (which copied the runfiles into `$RUNFILES/<main repo>/external/<external repo>/<path>` in addition to `$RUNFILES/<external repo>/<path>`. This flag was flipped to False in Bazel 8.0.0.

This is identical to the change made to rules_python in bazelbuild/rules_python#2516.

Work towards bazelbuild/rules_python#2581.

PiperOrigin-RevId: 721941173
copybara-service bot pushed a commit to protocolbuffers/protobuf that referenced this pull request Feb 1, 2025
Previously, the import path within the runfiles was only correct for the case `--legacy_external_runfiles=True` (which copied the runfiles into `$RUNFILES/<main repo>/external/<external repo>/<path>` in addition to `$RUNFILES/<external repo>/<path>`. This flag was flipped to False in Bazel 8.0.0.

This is identical to the change made to rules_python in bazelbuild/rules_python#2516.

Work towards bazelbuild/rules_python#2581.

PiperOrigin-RevId: 721941173
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

import paths from external Bazel modules are broken with Bazel 8.0.0
2 participants