nils måsén

The gzip issue is related to this problem with mono, not sure how we should work around that... Perhaps some special runtime checks need to be performed to avoid it......

This currently fails 4 tests, and I am not too eager in taking in a whole new Deflate implementation (1800 LoC 😓). I did some PoC testing in https://github.com/icsharpcode/SharpZipLib/commit/c9589cf493b8fe4f3146d2b72fc2847b068ece45 to...

Yeah, avoiding breaking changes is one of the guiding principles for maintaining the library, and this PR currently lacks the motivation for the change. It should be a fairly exotic...

Well, something tells watchtower to exit at > time="2023-01-21T20:00:01Z" level=info msg="Waiting for running update to be finished..." That is the message it prints when a `container stop` (or a `ctrl-c`)...

This time it was at 04. When are you rebooting it?

I guess you can add `--restart always` to your `docker run` command to have it restarted, but if this happens every night, the schedule will constantly shift and may never...

> When a file is used by another process, WriteEntry(TarEntry, bool) writes the entry, but obviously not the bytes (which is fine). That doesn't seem right. If the file is...

What `using` block are you referring to here? Wouldn't just putting a `try { WriteEntry(...) } catch (IOException) { ... }` work?

I think what you want is to be using `TarOutputStream` directly instead of using the `TarArchive` helper. It's meant for handling all the processing of files/paths etc and only requiring...

> I still think there is room for improvements. It should be possible to just move the `tarOut.PutNextEntry(entry)` inside the `File.Open` closure (and the directory case) in this case.