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

Fail the build on repository rule errors in a module extension #15796

Closed
wants to merge 1 commit into from

Conversation

fmeum
Copy link
Collaborator

@fmeum fmeum commented Jul 3, 2022

Fail the build on repository rule errors in a module extension

Also emit a Starlark stack trace pointing to the particular call site
of the repository rule.

Previously, the root cause error would be printed, but the build would
continue.

Fixes #14526 (comment)

@fmeum fmeum force-pushed the bzlmod-fail-module-extensions branch from e1bf4a4 to eac799d Compare July 3, 2022 14:05
@fmeum fmeum changed the title Fail the build due to repository rule errors in a module extension Fail the build on repository rule errors in a module extension Jul 3, 2022
@fmeum fmeum marked this pull request as ready for review July 3, 2022 14:20
@fmeum
Copy link
Collaborator Author

fmeum commented Jul 3, 2022

@Wyverald @meteorcloudy

@sgowroji sgowroji added team-ExternalDeps External dependency handling, remote repositiories, WORKSPACE file. awaiting-review PR is awaiting review from an assigned reviewer labels Jul 4, 2022
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.

Thank you so much!

@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 Jul 4, 2022
@fmeum
Copy link
Collaborator Author

fmeum commented Jul 4, 2022

@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 Jul 4, 2022
@meteorcloudy
Copy link
Member

@bazel-io fork 5.3.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 Jul 4, 2022
Also emit a Starlark stack trace pointing to the particular call site
of the repository rule.

Previously, the root cause error would be printed, but the build would
continue.

Fixes bazelbuild#14526 (comment)
@fmeum fmeum force-pushed the bzlmod-fail-module-extensions branch from eac799d to 7db6ea1 Compare July 4, 2022 14:39
Copy link
Collaborator Author

@fmeum fmeum left a comment

Choose a reason for hiding this comment

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

Done!

@sgowroji sgowroji removed the awaiting-PR-merge PR has been approved by a reviewer and is ready to be merge internally label Jul 5, 2022
@copybara-service copybara-service bot closed this in 0062f89 Jul 5, 2022
sgowroji pushed a commit to sgowroji/bazel that referenced this pull request Jul 14, 2022
Fail the build on repository rule errors in a module extension

Also emit a Starlark stack trace pointing to the particular call site
of the repository rule.

Previously, the root cause error would be printed, but the build would
continue.

Fixes bazelbuild#14526 (comment)

Closes bazelbuild#15796.

PiperOrigin-RevId: 459065865
Change-Id: I2444378c7857b1031fabfacd00f8246583bb2146
@ckolli5
Copy link

ckolli5 commented Jul 19, 2022

Hey @fmeum , we are trying to cherry-pick these changes to release-5.3.0. But pre-submit checks are failing due to missing dependencies. So, could you please help us in cherry picking these changes to release-5.3.0?

@fmeum fmeum deleted the bzlmod-fail-module-extensions branch July 20, 2022 07:09
fmeum added a commit to fmeum/bazel that referenced this pull request Jul 20, 2022
Fail the build on repository rule errors in a module extension

Also emit a Starlark stack trace pointing to the particular call site
of the repository rule.

Previously, the root cause error would be printed, but the build would
continue.

Fixes bazelbuild#14526 (comment)

Closes bazelbuild#15796.

PiperOrigin-RevId: 459065865
Change-Id: I2444378c7857b1031fabfacd00f8246583bb2146
fmeum added a commit to fmeum/bazel that referenced this pull request Jul 20, 2022
Fail the build on repository rule errors in a module extension

Also emit a Starlark stack trace pointing to the particular call site
of the repository rule.

Previously, the root cause error would be printed, but the build would
continue.

Fixes bazelbuild#14526 (comment)

Closes bazelbuild#15796.

PiperOrigin-RevId: 459065865
Change-Id: I2444378c7857b1031fabfacd00f8246583bb2146
fmeum added a commit to fmeum/bazel that referenced this pull request Jul 20, 2022
Fail the build on repository rule errors in a module extension

Also emit a Starlark stack trace pointing to the particular call site
of the repository rule.

Previously, the root cause error would be printed, but the build would
continue.

Fixes bazelbuild#14526 (comment)

Closes bazelbuild#15796.

PiperOrigin-RevId: 459065865
Change-Id: I2444378c7857b1031fabfacd00f8246583bb2146
@fmeum
Copy link
Collaborator Author

fmeum commented Jul 20, 2022

@ckolli5 The patch doesn't apply cleanly. You can close #15802.

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.

print in a module appears to be different from print in a workspace rule
6 participants