-
-
Notifications
You must be signed in to change notification settings - Fork 80
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
Command fails from extension but succeeds in my terminal #265
Comments
I think what's happening is you need to run a build or something to actually create all necessary analysis files. Eg
will fail, but if you run
and then run
again it will work. If you turn on "Queries Share Server" and force VS Code to build some target, I would expect this to work. It at least fixes "Bazel Build Targets" in the sidebar which has never worked for me. |
The bazel query used to introspect the targets available assumes that the generated files are already there. This creates the problem that you have to first generate the files once. bazel-contrib#265 Not sharing the same server makes it harder because the output is a random one. This means that for a normal user, it will be hard to make it work when query does not use the same server like your normal bazel queries. Because of that, it is better to have the queriesShareServer to true by default and the expert users can set it to false if they want.
Same issue here. Tried with "Queries Share Server" and without, same issue.
Where scala dep is:
But this command works if I run it manually in my terminal:
|
Duplicate of #216 |
I seem to be getting errors when using almost any Bazel command from the palette, as shown below.
I've tried running the same command in the terminal and it succeeds if and only if I'm adding quotations around the query.
The text was updated successfully, but these errors were encountered: