-
Updated
Jun 4, 2021 - Go
backup
Here are 3,614 public repositories matching this topic...
-
Updated
Apr 26, 2021 - Shell
-
Updated
Jun 3, 2021 - JavaScript
Describe the problem/challenge you have
When restoring a pod from a backup, restic is going through an error and reboot with a custom restic image name.
After this reboot, it starts to restore the namespace but using an image from the public repo available on the web instead of the custom image name previously configured.
Describe the solution you'd like
Is there a way to conf
What went wrong?
I'm getting deprecation warnings with openSSL encryption.
[2019/09/05 08:38:52][info] Using Encryptor::OpenSSL to encrypt the archive.
[2019/09/05 08:40:22][warn] Pipeline STDERR Messages:
[2019/09/05 08:40:22][warn] (Note: may be interleaved if multiple commands returned error messages)
[2019/09/05 08:40:22][warn]
[2019/09/05 08:40:22][warn] *** WARNING : depre
The class BackupDestination with function 'write' writes the backup file towards for example S3, but when f.e. S3MultipartUploadException occurs, the flysystem class returns 'false' instead of the exception. The backup is still marked as succesful.
-
Updated
May 15, 2021 - Python
-
Updated
Mar 18, 2021 - Python
General information
- App version: v0.8.0
- App source: Google Play
- Android Version: 9.0
Expected result
The activity org.shadowice.flocke.andotp.Activities.PanicResponderActivity should be protected.
andOTP should restrict which applications can launch the Activity.
What does happen instead?
There are two attack scenarios:
- Any application can sta
-
Updated
Jan 26, 2021 - Go
-
Updated
May 9, 2021 - Shell
-
Updated
Jun 5, 2021 - Perl
-
Updated
May 20, 2021 - C++
-
Updated
Apr 12, 2021 - PHP
-
Updated
Apr 8, 2021 - PHP
-
Updated
Jun 1, 2021 - Python
-
Updated
May 19, 2021 - Python
-
Updated
May 26, 2021 - Python
-
Updated
May 19, 2021 - Python
-
Updated
May 6, 2021 - Go
-
Updated
Apr 25, 2021 - Python
Improve this page
Add a description, image, and links to the backup topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the backup topic, visit your repo's landing page and select "manage topics."
the borg files cache can be rather large, because it keeps some information about all files that have been processed recently.
lz4 is a very fast compression / decompression algorithm, so we could try to use it to lower the in-memory footprint of the files cache entries.
before implementing this, we should check how big the savings typically are - to determine whether it is worthwhile doing