Skip to content

Comments

Fix for --incompatible_no_implicit_file_export#122

Merged
keith merged 1 commit intokeith:mainfrom
lukasoyen:fix-incompatible_no_implicit_file_export
Aug 29, 2025
Merged

Fix for --incompatible_no_implicit_file_export#122
keith merged 1 commit intokeith:mainfrom
lukasoyen:fix-incompatible_no_implicit_file_export

Conversation

@lukasoyen
Copy link
Contributor

@lukasoyen lukasoyen commented Jul 18, 2025

Currently the toolchain references the downloaded buildifier/buildozer by the downloaded filename and ignores the filegroup() generated by http_file(). This breaks bazel visibility checking if we try to run bazel test //.. --incompatible_no_implicit_file_export.

We are already specifying a downleaded_file_path to http_file(), so referencing the generated :file target will work on all platforms.

@hofbi
Copy link

hofbi commented Aug 29, 2025

@keith ping

Currently the toolchain references the downloaded buildifier/buildozer
by the downloaded filename and ignores the `filegroup()` generated by
`http_file()`. This breaks bazel visibility checking if we try to
run `bazel test //.. --incompatible_no_implicit_file_export`.

We are already specifying a `downleaded_file_path` to `http_file()`,
so referecing the generade `:file` target will work on all platforms.
@keith keith force-pushed the fix-incompatible_no_implicit_file_export branch from b42d9e6 to 4253acf Compare August 29, 2025 16:32
@keith keith enabled auto-merge (squash) August 29, 2025 16:46
@keith keith merged commit 225bf6a into keith:main Aug 29, 2025
3 checks passed
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.

3 participants