Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Interferes with ibazel

See original GitHub issue

Using the vscode plugin, every time a file is saved it seems to do same bazel query calls to the local bazel server.

If you’re also running a watch mode at the same time, it takes a long time to get a result in the ibazel session because the server is locked:

Build graph changed: "/usr/local/google/home/alexeagle/Projects/angular-bazel-example/src/lib/shorten/BUILD.bazel". Requerying...
Querying for files to watch...
Starting local Bazel server and connecting to it...
Loading: 0 packages loaded
Loading: 9 packages loaded
    currently loading: @build_bazel_rules_nodejs//internal/web_package ... (12 packages)
Loading: 375 packages loaded

Loading: 375 packages loaded
Another command holds the client lock: 
pid=147569
owner=client
cwd=/usr/local/google/home/alexeagle/Projects/angular-bazel-example

Waiting for it to complete...
Another command holds the client lock: 
pid=147575
owner=client
cwd=/usr/local/google/home/alexeagle/Projects/angular-bazel-example

Waiting for it to complete...
Starting local Bazel server and connecting to it...
Loading: 0 packages loaded
Loading: 0 packages loaded
Loading: 375 packages loaded

Loading: 375 packages loaded
Runing //src:devserver
Notifying of changes
Loading: 
Loading: 0 packages loaded
Analyzing: target //src:devserver (0 packages loaded, 0 targets configured)
Analyzing: target //src:devserver (5 packages loaded, 26419 targets configured)
INFO: Analysed target //src:devserver (5 packages loaded, 26424 targets configured).
INFO: Found 1 target...
[0 / 3] [-----] BazelWorkspaceStatusAction stable-status.txt
[27 / 40] checking cached actions
[43 / 48] Compiling TypeScript (devmode) //src/lib/shorten:shorten; 0s worker
[45 / 48] Compiling Angular templates (ngc) //src/app/hello-world:hello-world; 0s worker
[45 / 48] Compiling Angular templates (ngc) //src/app/hello-world:hello-world; 1s worker
[46 / 48] Compiling Angular templates (ngc) //src/app:app; 0s worker
Target //src:devserver up-to-date:
  dist/bin/src/devserver_launcher.sh
  dist/bin/src/devserver
INFO: Elapsed time: 10.939s, Critical Path: 6.00s
INFO: 4 processes: 4 worker.
INFO: Build completed successfully, 9 total actions
INFO: Build completed successfully, 9 total actions
SUCCESS
Error writing success to stdin: write |1: broken pipe
Triggering live reload
requesting reload: reload

somehow these two need to play nicely together

Issue Analytics

State:
Created 4 years ago
Comments:11 (5 by maintainers)

Top GitHub Comments

1reaction

muratbesercommented, Mar 26, 2020

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.

0reactions

muratbesercommented, Mar 26, 2020

@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.

Top Results From Across the Web

Building TypeScript Projects with Bazel - Minko Gechev

Bazel Build TypeScript. In this blog post, we'll make a brief introduction to what Bazel is and how we can build our TypeScript...

Angular Project with Bazel needs sudo to start - Stack Overflow

I just re-cloned the repository.

59192 (py36-tensorflow @2.0.0: does not build) - MacPorts Trac

I experience what seems to be a similar problem (segmentation fault during build) for py37-tensorflow @2.0.0 with macOS 10.15 and Xcode 11.1.

Troubleshooting guide for Bazel-on-Windows? - Google Groups

I had a similar problem myself, even though I was building Java, but I still needed a ... /Ibazel-out/vc_14_0_x64-fastbuild/genfiles/external/bazel_tools ...

C1001 Internal Compiler error (Compiling TF with XLA)

... /Ibazel-out/x64_windows-opt/bin/external/com_google_absl /Iexternal/nsync ... line 187) To work around this problem, try simplifying or changing the ...