[pull] master from rclone:master #112
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![pull[bot]](https://avatars.githubusercontent.com/in/12910?s=60&v=4){kind=small}
Bumps [docker/setup-qemu-action](https://github.com/docker/setup-qemu-action) from 2 to 3. - [Release notes](https://github.com/docker/setup-qemu-action/releases) - [Commits](docker/setup-qemu-action@v2...v3) --- updated-dependencies: - dependency-name: docker/setup-qemu-action dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
Before this change, the metadata map could be accessed from multiple goroutines at once, sometimes causing this error. This fix adds a global mutex for adjusting the metadata map to make all accesses safe. See: https://forum.rclone.org/t/azure-blob-storage-with-vfs-cache-concurrent-map-writes-exception/41686
Before this change the b2 backend listed all the buckets to turn a single bucket name into an ID. However in July 26, 2018 a parameter was added to the list buckets API to make listing all the buckets unecessary. This code sets the bucketName parameter so that only the results for the desired bucket are returned.
Before this change the b2 backend wasn't writing the metadata to the
object properly after a multipart upload.
The symptom of this was that sometimes it would give the error:
corrupted on transfer: sizes differ XXX vs 0
This was fixed by returning the metadata in the chunk writer and setting it in Update.
See: https://forum.rclone.org/t/multipart-upload-to-b2-sometimes-failing-with-corrupted-on-transfer-sizes-differ/41829
Before this change, the rclone rc command wouldn't actually report the error as a JSON blob which is inconsitent with what the HTTP API does. This change make sure we always report a JSON error, making a synthetic one if necessary. See: https://forum.rclone.org/t/when-using-rclone-rc-commands-somehow-return-errors-as-parsable-json/41855 Co-authored-by: Fawzib Rojas
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
See Commits and Changes for more details.
Created by
pull[bot]
Can you help keep this open source service alive? 💖 Please sponsor : )