You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm regularly, but not on every launch, seeing this on the CLI when using Bazel in a Terminal while having VSC open with vscode-bazel:
$ bazelisk test //...
WARNING: Running Bazel server needs to be killed, because the startup options are different.
Starting local Bazel server and connecting to it...
INFO: Analyzed 26 targets (184 packages loaded, 2481 targets configured).
INFO: Found 12 targets and 14 test targets...
(...)
and I suspect that the "other" Bazel server is one launched by vscode-bazel (because I'm not running anything else).
I DO use "bazel.queriesShareServer": true due to #261, #223, #216 (as well as "bazel.executable": "bazelisk").
Wondering if there is a way to avoid this.
The text was updated successfully, but these errors were encountered:
I'm regularly, but not on every launch, seeing this on the CLI when using Bazel in a Terminal while having VSC open with
vscode-bazel
:and I suspect that the "other" Bazel server is one launched by
vscode-bazel
(because I'm not running anything else).I DO use
"bazel.queriesShareServer": true
due to #261, #223, #216 (as well as"bazel.executable": "bazelisk"
).Wondering if there is a way to avoid this.
The text was updated successfully, but these errors were encountered: