bloomreach/s4cmd

s4cmd mv -r odd behavior

Open

#149 opened on Apr 10, 2019

View on GitHub
 (0 comments) (1 reaction) (0 assignees)Python (210 forks)auto 404
buggood first issue

Repository metrics

Stars
 (1,394 stars)
PR merge metrics
 (PR metrics pending)

Description

Hi guys,

I'm not sure what happened when I used s4cmd mv -r but I ran the command

s4cmd mv -r s3://bucket/folder1 s3://bucket/folder2

and now when I run s4cmd ls s3://bucket/folder2 I see the following

                 DIR s3://bucket/folder2/subdir/
2019-04-10 22:56   0 s3://bucket/folder2/.
2019-04-10 23:08   0 s3://bucket/folder2/subdir

And I don't quite understand what's going on now b/c when I ran s4cmd ls s3://bucket/folder1 before the move I got

                 DIR s3://bucket/folder1/subdir/
2019-02-28 23:01   0 s3://bucket/folder1/

This doesn't seem right. Is there something I should have done, and is there someway to recover the old structure?

Contributor guide

Research direction
Inspect the s4cmd mv r command implementation in the source code to understand how it handles recursive directory moves. Trace the logic for creating zero byte files and directories. Check if there is a known issue with the handling of trailing slashes or directory markers.
Tech stack
python
Domain
cli
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitPython
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65