Michael Eischer
Michael Eischer
What does this PR change? What problem does it solve? ----------------------------------------------------- On Windows, creating a backup could sometimes print the following error ``` error: nodeFromFileInfo [...]: get named security info...
What does this PR change? What problem does it solve? ----------------------------------------------------- The HTTP client can only retry HTTP2 requests after receiving a GOAWAY response if it can rewind the body....
What does this PR change? What problem does it solve? ----------------------------------------------------- Document how to recover from `cannot encode tree at "[...]" without loosing information` errors. In addition, document basic requirements...
What does this PR change? What problem does it solve? ----------------------------------------------------- Restic 0.17.0 introduced monitoring for stuck backend requests. This works well in general, however, for busy backends or very...
What does this PR change? What problem does it solve? ----------------------------------------------------- - Split description for non-Amazon S3 providers into a separate section. That section now also includes the `s3.bucket-lookup` extended...
What does this PR change? What problem does it solve? ----------------------------------------------------- See the first commit for the main changes. The docs for the `backup` command now link to the scripting...
Decrypting the credentials requires a lot of memory, such that later garbage collections only happen after doubling that memory usage again. Explicitly run a GC to reset the memory usage...
The policy can be reused, thus there's no need to recreate it for every processed calendar event. Inspired by https://github.com/inovex/CalendarSync/issues/180 . But this barely changes the memory usage.
Enabling data race detection should be sufficient for release builds. Helps with https://github.com/inovex/CalendarSync/issues/180 when building from source. Release builds never used that flag.
As the whole request body is read using io.ReadAll, thus the request can be freed immediately afterwards. Might help with https://github.com/inovex/CalendarSync/issues/180 .