-
-
Notifications
You must be signed in to change notification settings - Fork 82
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Revert "Make queries share the same server by default (#270)" #355
Revert "Make queries share the same server by default (#270)" #355
Conversation
)" This reverts commit 64c9d7e. The underlying issue that this addresses is now fixed in Bazel 7.1.0. See bazel-contrib#216 and bazelbuild/bazel#21505.
Do we know which percentage of the user-base of this extension is already using Bazel 7.1? From the perspective of most Bazel 7.0 or 6.x users which might not be aware that this issue existed in Bazel < 7.1, this VSCode extension will seem broken. Should we rather auto-detect the Bazel version and set the setting automatically based on that? Or at least display a warning for older Bazel versions? |
Good point. I think displaying a message for older versions would be good, since this also has a manual workaround of adding the convenience symlinks to |
This flips the `bazel.queriesShareServer` default back to `true`, since I think it was a bit hasty in bazel-contrib#355 to break everyone not on the latest bazel version. Instead, I have added a section to the docs, linked from the setting, describing how to safely disable this option.
This flips the `bazel.queriesShareServer` default back to `true`, since I think it was a bit hasty in bazel-contrib#355 to break everyone not on the latest bazel version. Instead, I have added a section to the docs, linked from the setting, describing how to safely disable this option.
@vogelsgesang I've put up a PR to revert this change, plus add some docs in #367. |
This flips the `bazel.queriesShareServer` default back to `true`, since I think it was a bit hasty in bazel-contrib#355 to break everyone not on the latest bazel version. Instead, I have added a section to the docs, linked from the setting, describing how to safely disable this option.
This flips the `bazel.queriesShareServer` default back to `true`, since I think it was a bit hasty in #355 to break everyone not on the latest bazel version. Instead, I have added a section to the docs, linked from the setting, describing how to safely disable this option.
This reverts commit 64c9d7e.
The underlying issue that this addresses is now fixed in Bazel 7.1.0. See #216 and bazelbuild/bazel#21505.