bloomreach / bloomreach/s4cmd

Do not throw exception if file exists

Open
#188 2 comments 1 reaction 0 assignees View on GitHub
Dominant language
Python
Stars
1.4k
Forks
209
PR merge metrics
No merged PRs in 30d

Description

Version from pip3 - 2.1.0 - crashes when a file already exists in the bucket:

```
(s4cmd) $ s4cmd put bla.zip s3://bla/bla/
[Runtime Failure] File already exists: s3://bla/bla/bla.zip
Exception in thread Thread-1:ead(s)]
Traceback (most recent call last):
[Thread Failure] File already exists: s3://bla/bla/bla.zip
```

I wonder if an exception is unavoidable or if s3 can return an error to evaluate. I also think the exception needs to be caught and treated.

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by reproducing the `s4cmd put bla.zip s3://bla/bla/` command against a bucket containing the target file, then trace the resulting runtime and thread failures. Done means an existing destination is handled without an uncaught exception, with behavior consistent with the intended S3 error response.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
cli
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 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.