Skip to content

Conversation

@fmeum
Copy link
Collaborator

@fmeum fmeum commented Aug 18, 2023

When passed to print or fail, a module extension tag now results in a string such as 'foo' tag at /ws/MODULE.bazel:3:4, which can be used to form error messages referencing tags without leaking non-hermetic information to the extension implementation function.

@github-actions github-actions bot added awaiting-review PR is awaiting review from an assigned reviewer team-ExternalDeps External dependency handling, remote repositiories, WORKSPACE file. labels Aug 18, 2023
When passed to `print` or `fail`, a module extension tag now results in
a string such as `'foo' tag at /ws/MODULE.bazel:3:4`, which can be used
to form error messages referencing tags without leaking non-hermetic
information to the extension implementation function.
Copy link
Member

@meteorcloudy meteorcloudy left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Awesome, thanks!

@meteorcloudy meteorcloudy added awaiting-PR-merge PR has been approved by a reviewer and is ready to be merge internally and removed awaiting-review PR is awaiting review from an assigned reviewer labels Aug 18, 2023
@fmeum
Copy link
Collaborator Author

fmeum commented Aug 18, 2023

@bazel-io flag

@bazel-io bazel-io added the potential release blocker Flagged by community members using "@bazel-io flag". Should be added to a release blocker milestone label Aug 18, 2023
@meteorcloudy
Copy link
Member

@bazel-io fork 6.4.0

@bazel-io bazel-io removed the potential release blocker Flagged by community members using "@bazel-io flag". Should be added to a release blocker milestone label Aug 18, 2023
@github-actions github-actions bot removed the awaiting-PR-merge PR has been approved by a reviewer and is ready to be merge internally label Aug 18, 2023
iancha1992 pushed a commit to iancha1992/bazel that referenced this pull request Aug 18, 2023
When passed to `print` or `fail`, a module extension tag now results in a string such as `'foo' tag at /ws/MODULE.bazel:3:4`, which can be used to form error messages referencing tags without leaking non-hermetic information to the extension implementation function.

Closes bazelbuild#19274.

PiperOrigin-RevId: 558163928
Change-Id: If20086c62356bb0635d0a4bdf91029267122f62b
@fmeum fmeum deleted the fail-on-tag branch August 21, 2023 11:32
meteorcloudy pushed a commit that referenced this pull request Aug 22, 2023
…sages (#19285)

When passed to `print` or `fail`, a module extension tag now results in
a string such as `'foo' tag at /ws/MODULE.bazel:3:4`, which can be used
to form error messages referencing tags without leaking non-hermetic
information to the extension implementation function.

Closes #19274.

Commit
cc5889c

PiperOrigin-RevId: 558163928
Change-Id: If20086c62356bb0635d0a4bdf91029267122f62b

Co-authored-by: Fabian Meumertzheim <[email protected]>
Co-authored-by: Xùdōng Yáng <[email protected]>
@iancha1992
Copy link
Member

The changes in this PR have been included in Bazel 6.4.0 RC1. Please test out the release candidate and report any issues as soon as possible. If you're using Bazelisk, you can point to the latest RC by setting USE_BAZEL_VERSION=last_rc.
Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

team-ExternalDeps External dependency handling, remote repositiories, WORKSPACE file.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants