Michael Eischer

I did a bit of memory profiling. The memory usage peak is probably mostly caused by https://github.com/inovex/CalendarSync/blob/ccdebc534f875ae0c3a6aa2fd3ee185a553e3ea8/internal/auth/storage_encryption.go#L38 . At least on my machine that allocate a whopping 256MB of memory....

Btw, I've used the following patch for memory profiling (run `go mod tidy` to get the library) ```diff diff --git a/cmd/calendarsync/main.go b/cmd/calendarsync/main.go index 3cb4ac6..de2b3cc 100644 --- a/cmd/calendarsync/main.go +++ b/cmd/calendarsync/main.go @@...

The underlying problem here is that `FindFilteredSnapshots` which is used to list the snapshots, does not report errors to its caller and instead just prints an `Ignoring [...]` message. Sorting...

The `Corrupted blobs are either caused by hardware issues or software bugs.` error CANNOT in any way be affected by the state of the existing repository. This error message didn't...

What is your use case exactly? Would a command to check whether a repository already exist be more useful for your use case?

@iheartski `run_restic cat config` would probably be a lot faster to check whether a repository exists.

Restic binaries are already fully reproducible, see https://restic.readthedocs.io/en/stable/developer_information.html#reproducible-builds . Due to how the restic binaries are currently signed, we cannot build them on Github. But that doesn't matter much as...

Related to #3821

I think your steps to reproduce are broken. With the given steps, all files in the backup source folder are excluded, such that the snapshot is empty - just as...

It quite the contrary, there's no documentation that a special syntax `./` exists. Although I have to agree that not normalizing paths at all would make more sense. I guess...