Interferes with ibazel about vscode-bazel

[muratbeser]

I'm still having this issue. I'm runing iBazel via npx.

also I have no idea what causes the .bazel_fix_comands.json warning.

[allevato]

When you say "every time a file is saved", do you mean any file in the workspace, or just BUILD files? We have logic to do a query when a BUILD file is saved so that the Bazel Build Targets tree view is automatically updated if you add/remove targets, but it shouldn't be triggered for other files.

I don't know much about ibazel, so it's not immediately clear to me what the resolution is here.

[alexeagle]

https://github.com/bazelbuild/bazel-watcher is the "watch mode" for Bazel and it's somewhere in between community contrib and Bazel first-party supported.

Yes, I believe the change I was making there was to a BUILD file.

[mariusgrigoriu]

This isn't just a problem with ibazel. The lock prevents regular bazel commands from running in the terminal.

[achew22]

Could we put together a gist that demonstrated the issue at hand? I think that would provide some much needed clarity

[mariusgrigoriu]

I don't have a repro available, but I observed this during a live share session.

The Bazel docs recommend setting --output_base if you are scripting queries to avoid contending for the lock. https://docs.bazel.build/versions/master/guide.html#choosing-the-output-base

[alexeagle]

Another major flaw is when the user runs bazel with some startup flags that differ from vscode extension. Then they see the Bazel server restarting for every command they run.

[thomasvl]

Another major flaw is when the user runs bazel with some startup flags that differ from vscode extension. Then they see the Bazel server restarting for every command they run.

Trunk already has prefs to allow adding other options to the invokes the extension does.

[allevato]

With #160 merged, I think we can close this out. The next version of the extension will by default use a separate --output_base for queries, which should resolve issues with ibazel (and other uses of query from the extension during long-running build tasks). Thanks to @mariusgrigoriu for pointing us at the tip about that in the docs!

[thomasvl]

The 0.3.0 release was in September, the fix listed here was landed in Dec, so unless you built your own copy of the extension you likely don't have the fix yet.

[muratbeser]

@thomasvl no it is not. with npx or with yarn ibazel commands I do have the same issue yarn ibazel has perfomance impact. it might be my setup I'm not sure. currently I run this too often.