tree 8629204ae7951d416066a2348bd4e97f5bc22819
parent 7ef0841386f52a555b4b1f7a3cf325b00ab4ea23
author Michal Terepeta <michalt@google.com> 1620027358 +0000
committer commit-bot@chromium.org <commit-bot@chromium.org> 1620027358 +0000

React when Bazel/Blaze prefix changes

Previously if no Bazel/Blaze symlinks were present, we defaulted to the
`bazel-*` ones and never checked if that assumption was accurate. This
change starts watching the symlinks and recreates the analysis contexts
if a symlink gets added. This way we'll run the `BazelWorkspace` code
again and use the correct paths.

This is quite important since `bazel/blaze clean` does remove the
symlinks so if the analysis server starts at such a point, we would
never find any generated files if the workspaced turned out to be a
Blaze one.

Bug: http://b/175087705
Change-Id: If7bb21c7d69a3092832c18004691d56949e5af54
Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/197540
Reviewed-by: Konstantin Shcheglov <scheglov@google.com>
Commit-Queue: Michal Terepeta <michalt@google.com>