go_repository: avoid unnecessary fetches in HTTP mode #1206
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Currently, if a
go_repository
rule is in HTTP mode and hasbuild_file_generation = on
it can result in unnecessary calls todownload_and_extract
while the@bazel_gazelle_go_repository_tools
and@bazel_gazelle_go_repository_cache
labels are still not available. Note that redundant fetches can be unavoidable when in HTTP mode andbuild_file_generation = auto
because the rule needs to fetch and examine the repo to determine if it requires@bazel_gazelle_go_repository_tools
.For more info about repository rule restarting see:
https://docs.bazel.build/versions/5.0.0/skylark/repository_rules.html#when-is-the-implementation-function-executed
Resolve #1175