New plugin available: Cloud (access to Box, Dropbox, etc).

[Ovg]

Total Commander 10.51 RC3 x64
Cloud Plugin v 2.5

1. Can't copy to yandex.disk files witch names starts with # character
2. If a file name contains # character, # and all characters after it (include extension) will be deleted upon copying to yandex.disk
3. Can't copy from yandex.disk files witch names contains % or # characters

[ghisler(Author)]

I can confirm the problem with Yandex only. You can still rename such files with Shift+F6 to download them.

[Ovg]

Yes, rename working fine, but maybe you can do something with this problem?

[ghisler(Author)]

It's on my to do list. I probably just need to encode the character.

[Ovg]

2ghisler(Author)
Many thanks!

[Jon Canale]

TC 10.51 on Win10-64Pro and Using Cloud plugin 2.50Beta4

Can't connect to my Google Drive with TC & Cloud plugin today. Has worked seamlessly for a long time. Can connect with Firefox and Google.

TC goes out to get "key", but then closes connection with this message:

HTTP/ received, closing
POST /o/oauth2/token HTTP/1.1
200 OK
CONNECT \GoogleDrive-personal
=================
Get dir: \
HTTP error: Name not resolved
HttpSendRequest failed: Name not resolved
Disconnected

I rebooted as well - still no luck...

[Jon Canale]

Maybe false alarm. I tried logging into my Dropbox account with TC. It worked fine. Then I tried logging into the GDrive again - now it works!

[Usher]

2ghisler(Author)
1. Could you add timestamps to Cloud logs? It's annoying to read error messages when uploading big files:

202 Accepted
HTTP error: Connection reset
HTTP error: Timeout
HTTP error: Connection reset
HTTP error: Connection reset
HTTP error: Connection reset
HTTP error: Connection reset
HTTP error: Connection reset
HTTP error: Connection reset
HTTP error: Connection reset
HTTP error: Connection reset

2. Cloud plugin ignores these errors and continues uploading. The file will not be saved, but TC ends upload with no error message. it's just a waste of time.

[ghisler(Author)]

Strange, it should warn about upload errors. What file types are you trying to upload?

[Usher]

2ghisler(Author)
They are large (300 MB+) 7z archives. Without timestamps you can't see that the plugin started upload successfully and continued it for a several minutes before the first connection reset.
I have no similar problems with GoogleDrive, it happens only with OneDrive. I haven't tested Dropbox and other cloud drives.
Edit: I use the latest plugin version 3.50b4.

[ghisler(Author)]

It may be a timeout issue AFTER the upload completes (100% progress): Some cloud services scan the uploaded file for malicious content, and this can take a long time when uploading such large files.

[Usher]

No, there are definitely errors during upload. Upload is slow and takes several minutes. I can read error messages in a message box and see unfinished upload continued at the same time. I can make screenshots, but I can't prove it for sure without timestamps added to log - see my first point.

Edit: After such errors there seems to be some memory unreleased even with "Unload all plugin" commands and 32-bit TC crashes on close. I haven't tested 64-bit TC yet.

[ghisler(Author)]

OneDrive requires that large files are being uploaded in multiple chunks. The maximum allowed size for each chunk is 60 Megabytes, as described here:
https://learn.microsoft.com/en-us/onedrive/developer/rest-api/api/driveitem_createuploadsession?view=odsp-graph-online
My cloud plugin sends the file in chunks of 50 MBytes. According to your log, only the first chunk is accepted, afterwards you get "connection reset" errors, which means that the target closed the connection. The plugin does retry sending chunks when an upload fails, but this doesn't seem to help here.

[Usher]

2ghisler(Author)
Connection reset happens randomly. Some larger files (>500 MB) were uploaded without problems, some smaller files (<200 MB) were broken more than once, even after I cancelled upload and tried to reupload the file from the beginning. I have observed faster connection speed and practically no timeouts in the night so there may be some problems on the server side (f.e. too short expiration time for slow connections). Can you use smaller chunks for slower connection?

From the linked MS docs I can see that you can resume upload, but there is really a problem with API there:

The nextExpectedRanges property won't always list all of the missing ranges.

[ghisler(Author)]

I'm not using nextExpectedRanges, I'm just re-sending the last block if the upload fails.