rclone / rclone/rclone

Overlapping moves too conservative?

Open
#1,082 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug doc fix filtering thinking
Dominant language
Go
Stars
59.8k
Forks
5.4k
Avg merge
2d 14h
Merged PRs (30d)
48

Description

See the forum

rclone move crypt:/folder crypt:

and I get: Attempt 1/3 failed with 0 errors and: can't move files on overlapping remotes

Is this being more conservative that it needs to?

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the linked forum discussion and reproduce rclone move crypt:/folder crypt: to confirm the overlapping-remotes failure. Determine whether this move should be allowed and what the expected behavior is; no source file or test is identified in the issue.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
cli
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.