Thank you to everyone who tested the betas, reported bugs and sent in pull requests.
Especial thanks to Stefan Breunig who has agreed to help me maintain rclone and has made many contributions in the changelog below.
Headline features are FTP and HTTP backends, Google Team Drive support, Dropbox v2, rclone mount working on Windows, rclone ncdu (personal fave), --fast-list, --tpslimit (useful for rclone mount users) and lots of fixes!
Happy rclone-ing!
– Nick
v1.37 - 2017-07-22
New backends
FTP - thanks to Antonio Messina
HTTP - thanks to Vasiliy Tolstov
New commands
rclone ncdu - for exploring a remote with a text based user interface.
rclone lsjson - for listing with a machine readable output
rclone dbhashsum - to show Dropbox style hashes of files (local or Dropbox)
New Features
Implement --fast-list flag
This allows remotes to list recursively if they can
This uses less transactions (important if you pay for them)
This may or may not be quicker
This will user more memory as it has to hold the listing in memory
–old-sync-method deprecated - the remaining uses are covered by --fast-list
This involved a major re-write of all the listing code
Add --tpslimit and --tpslimit-burst to limit transactions per second
this is useful in conjuction with rclone mount to limit external apps
Add --stats-log-level so can see --stats without -v
Print password prompts to stderr - Hraban Luyat
Warn about duplicate files when syncing
Oauth improvements
allow auth_url and token_url to be set in the config file
Print redirection URI if using own credentials.
Don’t Mkdir at the start of sync to save transactions
Compile
Update build to go1.8.3
Require go1.6 for building rclone
Compile 386 builds with “GO386=387” for maximum compatibility
Bug Fixes
Fix menu selection when no remotes
Config saving reworked to not kill the file if disk gets full
Don’t delete remote if name does not change while renaming
moveto, copyto: report transfers and checks as per move and copy
Local
Add --local-no-unicode-normalization flag - Bob Potter
Mount
Now supported on Windows using cgofuse and WinFsp - thanks to Bill Zissimopoulos for much help
Compare checksums on upload/download via FUSE
Unmount when program ends with SIGINT (Ctrl+C) or SIGTERM - Jérôme Vizcaino
On read only open of file, make open pending until first read
Make --read-only reject modify operations
Implement ModTime via FUSE for remotes that support it
Allow modTime to be changed even before all writers are closed
Fix panic on renames
Fix hang on errored upload
Crypt
Report the name:root as specified by the user
Add an “obfuscate” option for filename encryption - Stephen Harris
Amazon Drive
Fix initialization order for token renewer
Remove revoked credentials, allow oauth proxy config and update docs
B2
Reduce minimum chunk size to 5MB
Drive
Add team drive support
Reduce bandwidth by adding fields for partial responses - Martin Kristensen
Implement --drive-shared-with-me flag to view shared with me files - Danny Tsai
Add --drive-trashed-only to read only the files in the trash
Remove obsolete --drive-full-list
Add missing seek to start on retries of chunked uploads
Fix stats accounting for upload
Convert / in names to a unicode equivalent (/)
Poll for Google Drive changes when mounted
OneDrive
Fix the uploading of files with spaces
Fix initialization order for token renewer
Display speeds accurately when uploading - Yoni Jah
Arg, I don’t believe it. I managed to miss that out of the mount docs!
I’ve added this to the docs
Installing on Windows
To run rclone mount on Windows, you will need to download and install WinFsp.
WinFsp is an open source Windows File System Proxy which makes it easy to write user space file systems for Windows. It provides a FUSE emulation layer which rclone uses combination with cgofuse. Both of these packages are by Bill Zissimopoulos who was very helpful during the implementation of rclone mount for Windows.
I agree with @ncw that it is best to report these issues on GitHub and cc me (billziss-gh) for faster resolution. However @FoGBaV 's problem is probably straightforward to resolve.
The issue appears to be the fact that drives created as Administrator are not visible by other accounts (including the account that was elevated as Administrator). So if you start a Windows drive from an Administrative Command Prompt and then try to access the same drive from Explorer (which does not run as Administrator), you will not be able to see the new drive.
The easiest way around this is to start the drive from a normal command prompt. It is also possible to start a drive from the SYSTEM account (using the WinFsp.Launcher infrastructure) which creates drives accessible from everyone on the system.
Additional information re: drive behavior on Windows:
Thanks for the update on the new release! The windows mount in particular is a great step forward , Well done!
Just wanted to quickly share my experience with it, As i was initially getting BSOD errors when attempting to access the mount point in Windows 10.
Found that AVAST antivirus has some kind of trigger in it that caused it to bring the whole system down - The error seemed to indicate a failure with “aswsnx.sys”.
Removing Avast AV has allowed me to proceed past this point but thought that there may be more like me in the same boat so am sharing it here!
@zaldre please file a github issue, so that I can track this. I have never seen a BSOD related to WinFsp (at least since it reached release quality), so something like this, even if caused by a third party product is very important. I would like to investigate it and determine if it is the fault of WinFsp and fix it if it is.
Please open an issue with WinFsp and attach the minidump. Please add all relevant information such as use of Avast AV, error message about aswsnx.sys, etc.
BTW, WinFsp includes public symbols in the directory: \Program Files (x86)\WinFsp\sym
EDIT: if you feel uncomfortable attaching a minidump in a public forum (like GitHub) you can also try running analyze -v from WinDbg, although you would have to set up NTOS symbols properly for this to produce useful info.