Fix a race condition that could cause the build graph to not be generated when doing initial background indexing #1652
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.
…
We were making the initial
generateBuildGraph
call inSourceKitLSPServer
from aTask
. This means thatgenerateBuildGraph
could be executed afterwaitForUpToDateBuildGraph
was called bySemanticIndexManager
. ThuswaitForUpToDateBuildGraph
returned immediately and no files were background indexed.Make
generateBuildGraph
immediately schedule a package reload for SwiftPM build systems instead of doing the hop through aTask
, fixing the race condition.rdar://135551812