-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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 locations reported in repo rule instantiation errors for extensions #23363
Conversation
Since `Rule` logic drops a call stack entry, errors during repo rule instantiation in a module extension weren't reported with a useful `Location`.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice, thanks!
@bazel-io fork 7.4.0 |
@meteorcloudy I fixed a test. |
Since `Rule` logic drops a call stack entry, errors during repo rule instantiation in a module extension weren't reported with a useful `Location`. Work towards bazelbuild#19055 Closes bazelbuild#23363. PiperOrigin-RevId: 665468188 Change-Id: If67b5b6f290ac4e33b5743e9c1c361a93e1217ef
The changes in this PR have been included in Bazel 7.4.0 RC1. Please test out the release candidate and report any issues as soon as possible. |
Since
Rule
logic drops a call stack entry, errors during repo rule instantiation in a module extension weren't reported with a usefulLocation
.Work towards #19055