Aleksa Sarai

I wouldn't mind adding timeouts, but it should be noted that this will not result in containers starting without issue -- it will result in containers failing to start in...

This reminds me of discussions we had several years ago about allowing self-LGTMs within OCI (with some OCI projects allowing it and then later disallowing it and vice-versa). I agree...

Moving to 1.3.0, since the spec change isn't out and we want a 1.2.0 release soon.

I also just ran into something very similar. This is with regular spinning rust drives connected via SATA (using a SAS expander) and there were no other IO-related errors in...

@leonard-slass Can you give an example of a bad lookup? The Japanese plugin uses the same logic as Yomichan which (while not perfect) almost always gives reasonable results for standard...

Hmmm. I've looked at this again. While I was wrong to say the format is not valid, casync prints every entry as though it's a `FullType` but it will happily...

systemd/casync#267 should fix the casync side, and #188 fixes the core issues with FullType though I still am not sure what we should do in the multiple-entries-for-the-same-path case. At the...

@tgolsson I'm not sure if there's a nice place to start necessarily. I think the best performance improvement we could make here is if we generate the mtree tree during...

But if you would like to help, taking a look at the `go-mtree` side of things would be appreciated. https://github.com/vbatts/go-mtree/issues/146 is the upstream bug (my comment from a few years...

FWIW, I have since figured out and fixed the issues in go-mtree (https://github.com/vbatts/go-mtree/pull/188 fixes the relevant issues for us to be able to use the FullType version of the manifest...