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.

Sign up for GitHub

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

Jump to bottom

[7.1.0] Do not record any repo mapping entries in the RepoMappingRecorder for WORKSPACE repo rules #21457

Merged
merged 1 commit into from
Feb 21, 2024
Merged

[7.1.0] Do not record any repo mapping entries in the RepoMappingRecorder for WORKSPACE repo rules #21457

merged 1 commit into from
Feb 21, 2024

Commits on Feb 21, 2024

  1. Do not record any repo mapping entries in the RepoMappingRecorder for… 

    … WORKSPACE repo rules

Follow-up to bazelbuild@1cbf09d; beyond not recording those entries in the marker file, we shouldn't even record them in memory in the first place. This avoids nasty problems with unexported repo rules (gah) and should be an extremely tiny performance win as a bonus...

Fixes bazelbuild#21451

PiperOrigin-RevId: 609010175
Change-Id: I90eb921b09068f327b42886ea0a1875374a94049
    @Wyverald @bazel-io
    Wyverald authored and bazel-io committed Feb 21, 2024
    Configuration menu
    Copy the full SHA
    5f4fad5 View commit details
    Browse the repository at this point in the history