What is the problem you are having with rclone?

Using rclone mount with a non-persistent configuration (all settings given by environment variables) & VFS caching enabled attempts to use a VFS cache dir with illegal characters (:) on Windows.

What is your rclone version (output from rclone version)

rclone v1.52.3
- os/arch: windows/amd64
- go version: go1.14.7

OS/Environment

None yet, but I'm working on OS X v10.11.6 'El Capitan' client-side. (See 'The way of deployment (cloud or local)' below for details on considered server infrastructure.)

Ansible version

None yet, as I haven't yet gotten that far into setting up Algo.

Version of components from requirements.txt

Not applicable (see above.)

Summary of the pro

As OpenSSL does not support asynchronous read/write duplex, sometimes, the asynchronous read/write logic needs to be changed to consecutive processing. An interface for viewing the job status in internal objects maybe helpful for this.

ASYNC_JOB *SSL_get_job(const SSL *s)
{
    return s->job;
}

Is your feature request related to a problem? Please describe.
When working with a big piece of text, I sometimes scroll down and copy some text into another tab. When switching back to the first tab, both the input and the output pane is back on top. So I don't know where I was working just now.

Describe the solution you'd like
After tab switching, scroll position should be remembere

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

Problem:

A common pattern is:

GUARD(s2n_stuffer_skip_write(stuffer, bytes_to_write));
uint8_t* ptr = suffer->blob.data + stuffer->write_cursor - bytes_to_write;

which could be simplified.

Solution:

*ptr could be an *out parameter to s2n_stuffer_skip_write

• Does this change what S2N sends over the wire? No.
• Does this change any public APIs? No.

E.g. accept missing leading 0

In osx/updater/updater.go, we're referencing an ancient Go package, which has moved to a new location. Right now, the updater doesn't build (should we test this on travis?).