Fix bazel build output group parsing during Indexing #537
Conversation
This file contains hidden or 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
BalestraPatrick
approved these changes
Jun 12, 2022
Base automatically changed from
bj/only-build-bazeldependencies-once-in-a-build
to
main
June 12, 2022 21:52
brentleyjones
force-pushed
the
bj/fix-bazel-build-output-group-parsing-during-indexing
branch
from
ba49147 to
c4e32a0
Compare
I'm not sure why dependent targets are allowed to run before `BazelDependencies` is finished, but at least during Index Build I've seen it happen. It might be limited to multiplatform builds.
brentleyjones
force-pushed
the
bj/fix-bazel-build-output-group-parsing-during-indexing
branch
from
c4e32a0 to
3f4b204
Compare
brentleyjones
deleted the
bj/fix-bazel-build-output-group-parsing-during-indexing
branch
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.
I'm not sure why dependent targets are allowed to run before
BazelDependenciesis finished, but at least during Index Build I've seen it happen. It might be limited to multiplatform builds.