Skip to content

Conversation

@fmeum
Copy link
Collaborator

@fmeum fmeum commented May 22, 2024

Catches a common gotcha of referencing a repo created by an extension elsewhere in an extension without a use_repo and provides actionable advice to user. This prevents lockfile corruption caused by non-visible labels.

The same validation is applied to labels in tag attributes.

Fixes #21845

@github-actions github-actions bot added team-ExternalDeps External dependency handling, remote repositiories, WORKSPACE file. awaiting-review PR is awaiting review from an assigned reviewer labels May 22, 2024
fmeum added 4 commits May 23, 2024 14:48
Catches a common gotcha of referencing a repo created by an extension elsewhere in an extension without a `use_repo` and provides actionable advice to user. This also prevents lockfile corruption caused by non-visible labels.
@fmeum fmeum force-pushed the 21845-invalid-ext-labels branch from 8c82249 to 45dc66c Compare May 23, 2024 14:18
@fmeum fmeum requested a review from Wyverald May 23, 2024 14:19
@fmeum fmeum force-pushed the 21845-invalid-ext-labels branch from 45dc66c to a1158b3 Compare May 23, 2024 14:23
@fmeum fmeum force-pushed the 21845-invalid-ext-labels branch from a1158b3 to 39a902a Compare May 23, 2024 14:26
Copy link
Member

@Wyverald Wyverald left a comment

Choose a reason for hiding this comment

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

This is quite nice!

@Wyverald Wyverald 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 May 23, 2024
@fmeum
Copy link
Collaborator Author

fmeum commented May 24, 2024

@bazel-io fork 7.2.0

@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 May 24, 2024
bazel-io pushed a commit to bazel-io/bazel that referenced this pull request May 24, 2024
Catches a common gotcha of referencing a repo created by an extension elsewhere in an extension without a `use_repo` and provides actionable advice to user. This prevents lockfile corruption caused by non-visible labels.

The same validation is applied to labels in tag attributes.

Fixes bazelbuild#21845

Closes bazelbuild#22495.

PiperOrigin-RevId: 636939357
Change-Id: Ib779207502f7767e4e8d3abc55ba7470f75821b9
github-merge-queue bot pushed a commit that referenced this pull request May 24, 2024
…xtensions (#22537)

Catches a common gotcha of referencing a repo created by an extension
elsewhere in an extension without a `use_repo` and provides actionable
advice to user. This prevents lockfile corruption caused by non-visible
labels.

The same validation is applied to labels in tag attributes.

Fixes #21845

Closes #22495.

PiperOrigin-RevId: 636939357
Change-Id: Ib779207502f7767e4e8d3abc55ba7470f75821b9

Commit
aa436c3

Co-authored-by: Fabian Meumertzheim <[email protected]>
@fmeum fmeum deleted the 21845-invalid-ext-labels branch May 24, 2024 19:04
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.

Using invalid patch path with bzlmod + lockfile results in crash and bad lockfile

2 participants