[change] bazel info call caching mechanism
#228
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
abrams27
approved these changes
Apr 21, 2022
lukaszwawrzyk
force-pushed
the
cache-bazel-info
branch
from
457175c
to
4533b7f
Compare
abrams27
changed the title
bazel info call caching
abrams27
changed the title
bazel info call cachingbazel info call caching mechanism
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Similarly to caching project between runs of the server I implemented caching for bazel info. Resolving bazel info is invoked for all endpoints, so for example when you restart IDE and want to run a build it will waste some time. Bazel info calls can be surprisingly long so it is best to avoid them if possible.