Geoff Jukes

I am having the same issue, with multiple files.

@christosts PR #1092 has been merged to main.

I'm not sure I agree. I use the FS-URLs a lot, an in that format, the bucket falls into the 'host' portion of the URL, and therefore it makes sense...

As `create` already exists (and pertains to the 'directory') and is 'on' by default, maybe `create_bucket`?

@poudro - The explanation does hold. Let me explain it differently.... In a POSIX filesystem, the full file path always exists. So you can 'stat' every part of it. So...

@poudro Are you saying that files uploaded by 2 users, with the same key prefix, result in an error? e.g. /some/place/user1.txt vs /some/place/user2.txt Or are the key prefixes different? e.g....

@poudro `s3://bucket/path/foo` does not imply that an object the object `s3://bucket/path/` exists, which is what causes the error you are seeing. When U1 creates the object at `s3://bucket/path/foo` are they...

It happens. I've experienced it myself many times. EDIT: https://docs.aws.amazon.com/AmazonS3/latest/userguide/managing-acls.html > Bucket and object permissions are independent of each other. An object does not inherit the permissions from its bucket....

@willmcgugan I didn't either, until recently, It's actually pretty simple: ``` s3.meta.client.copy_object( CopySource={ 'Bucket': src, 'Key': key }, Bucket=tgt, Key=new_key if new_key else key, StorageClass='STANDARD_IA' ) ``` where `src` and...

I used another service as a reference and downgraded everything to match. The combination below works just fine: ``` amqp==2.5.2 appdirs==1.4.3 boto3==1.9.41 botocore==1.12.253 certifi==2019.11.28 chardet==3.0.4 dnspython==1.16.0 docutils==0.15.2 eventlet==0.25.1 fs==2.4.11 fs-s3fs==1.1.1...