Delay missing-workspace warning until current-config fetch completes #21520
+90
−20
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.
Startup could emit “Failed to discover workspace…” before
linkedProjectsfromworkspace/didChangeConfigurationwas applied, even when a later fetch succeeded.Root cause: the initial fetch ran ahead of the config-driven reload, yielding a transient empty workspace and a misleading warning.
Track a lightweight config generation and gate the warning so it only fires after a fetch completes for the current configuration.
Added config_generation and last_workspace_fetch_generation, threaded generation through fetch requests, and recorded completion.
Warning emission is now gated on fetch completion for the current config; fetch flow unchanged.
Fixes #19567.
Tests: