When creating new bucket, check situations when it already exists #263

New Issue

Closed

opened 2023-07-29 01:10:34 +03:00 by inex · 3 comments

inex commented

2023-07-29 01:10:34 +03:00

Owner

Strange things may happen, which lead to server being unable to init repo.

def added the

Bug

Priority

High

labels 2023-07-29 01:13:22 +03:00

NaiJi commented

2023-08-03 09:20:52 +03:00

Collaborator

Could you elaborate how can I work around with it from the client side? What does it have to do with anything

inex commented

2023-08-03 15:21:46 +03:00

Poster

Owner

We generate the bucket name from the domain and server ID. There is a chance, that bucket with this name already exists. We do not handle this?

Also if it already exists, there may or may not be the actual backup repo we can work with.

We generate the bucket name from the domain and server ID. There is a chance, that bucket with this name already exists. We do not handle this? Also if it already exists, there may or **may not** be the actual backup repo we can work with.

NaiJi commented

2023-08-03 20:42:59 +03:00

Collaborator

Domain + server ID + DateTime.now().toString() ?

NaiJi self-assigned this 2023-12-02 21:58:04 +02:00

NaiJi referenced this issue from a commit

2023-12-02 22:44:48 +02:00

feat(backblaze): Include milliseconds since epoch to bucket name

NaiJi referenced this issue

2023-12-02 22:45:32 +02:00

feat(backblaze): Include milliseconds since epoch to bucket name #403

NaiJi closed this issue

2023-12-03 20:03:18 +02:00

No Milestone

No project

No Assignees

2 Participants

Notifications

Due Date

The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: SelfPrivacy/selfprivacy.org.app#263

There is no content yet.