I made a new release 1.1.15b1 for testing, see there:

https://github.com/borgbackup/borg/releases/tag/1.1.15b1

As you see, the borg code is pretty much the same as in 1.1.14, but especially the binary building got some updates. Thus, primarily the binaries should get some testing, to find issues before I make the final 1.1.15 release later this year.

As they were made on debian stretch wi

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

I presume following line should have higher loglevel to be visible even without debug logging as it is final state:
https://github.com/vmware-tanzu/velero/blob/718a94ad0565731780c904d27d09f27936f6b7d9/pkg/restore/restore.go#L616

See also vmware-tanzu/velero-plugin-for-vsphere#167

If you don't configure the destination disk properly, it will be very hard to understand what's happening because this message:

"Endpoints must be full URIs and include a scheme and host"

Is hidden by the exception handler:

public static function create(string $diskName, string $backupName): self
{
    try {
        $disk = app(Factory::class)->disk($diskName);

        

Is your feature request related to a problem? Please describe.
I've had several occasions when I wanted to retype the TOTP secret (not the code, but the secret key) from the edit dialog. For instance when transferring to a device which doesn't have a camera for the QR code. In all of those occasions I had issues recognizing 0s from Os.

Describe the solution you'd like
In the edit dial