Julio Merino

OK so now I'm confused. I thought you were concerned about the cost of the depset expansion + stating the files, which I think is going to be ~impossible to...

I've rebased my temporary code on top of master and removed the changes to the memory model in order to isolate the code to compute input sizes: https://github.com/bazelbuild/bazel/pull/19203 .

Now that the preparatory changes to calculate input sizes are in, it's time to tackle the model update but I'm not sure what the best way to go about this...

Interesting. I had seen this bug report earlier, but when I tried to reproduce it, I couldn't because I assumed it only happened with the graphics console. So thanks for...

Alright, sorry for the delay. I finally had a chance to look into it and the fix is trivial. It should be fixed on master in a moment and I'll...

Hmm, so the glibc version inconsistencies... I could expect (and I've recently been having to deal with that problem at work too, heh). Maybe the only reasonable path here is...

@sgowroji The repro details are in the description. Any sample run configuration fails in the way I described.

Any thoughts on what might be the trigger for this crash? We hadn't seen it before in our nightly coverage runs and now we are seeing it pretty consistently every...

I took a closer look at the java.log before the crash and saw: ``` 250602 22:10:45.953:W 76 [io.grpc.netty.NettyClientHandler$2.onGoAwayReceived] Received GOAWAY with ENHANCE_YOUR_CALM. Debug data: too_many_pings ``` My current theory is:...

I removed our custom keepalive flags, which apparently are mismatched with our Buildbarn deployment, and this made the GOAWAY messages disappear. However, Bazel _still_ crashed in the same way.