George Gensure

> Alternatively, you can also update the below config to double the value (instead of reverting): > > processing_timeout_millis That may not have the desired effect. The expectation is that...

There are two possible circumstances for the `client` member being null, both involve the client not being 'started'. I believe this to be a race condition with a transform for...

From a cursory look, this sounds like a great idea. I actually think the implementation is a little narrow-scoped though: with the worker doing all of the logic for this,...

Interesting. Did you happen to notice on the redis server what everyone was stuck doing? `client list` is my goto there. I'm going to presume they were idle, but if...

#428 has improved this situation a good bit, but there are still some missing items

> it's pretty clear that there are not enough direct memory to perform the copy operation. Therefore you might want to increase the size of direct memory by using `MaxDirectMemorySize=`....

You can attempt to modify the memory, but I'll also say that your filesystem CAS is very small for a real workload. 2 gigs per worker may induce over-expiration of...

This is the result of your bazel client and worker systems disagreeing about what constitutes a system-provided dependency, when bazel expects to be able to validate the conditions of the...

Are you running the worker on the bare localhost machine or a container? Assuming it is bare, the version printout you posted there is from `g++` based on the content....

Note the `/usr/bin/gcc` in that compilation. Run _that_ with -v to confirm it is 7, and as I'm sure it is, switch that (i.e. with `update-alternatives`) to 9 to correct...