lberki
lberki
Apparently, `--legacy_external_runfiles` is the silver lining of the cloud that is the fact that `--experimental_sibling_repository_layout` will apparently be left unflipped. I thought that we can't get away with flipping one...
Agreed; @Wyverald and @meteorcloudy might know something that makes (3) infeasible, though.
Created https://github.com/bazelbuild/bazel/pull/17943 as a prototype to fix this.
We ran into this again. This time, the stack traces show: ``` "tree-artifact-visitor-46" #1800 [144416] daemon prio=5 os_prio=0 cpu=28027.44ms elapsed=12463.90s tid=0x00007f b740001e70 nid=144416 runnable [0x00007fbb95efe000] java.lang.Thread.State: RUNNABLE at com.google.devtools.build.lib.vfs.inmemoryfs.InMemoryFileSystem.stat(InMemoryFileSystem.java:360) at...
@brandjon what's the impact of this issue? All things being equal, I'd much rather this doesn't take energy away from e.g. .bzl visibility and I don't immediately see why this...
Bumping this down to P2 to indicate our collective desire to get this into Bazel 6.0, but also that we won't postpone the release cut for this, should this and...
@oquenchil , can you take care of this? I have a little too much to do this week and the next :(
I don't _think_ this is going to work because this would probably break our internal tests for the reasons described [here](https://github.com/bazelbuild/bazel/issues/8319#issuecomment-865934356). I can imagine two possible resolutions: * @oquenchil runs...