Chewing_Bever
/
rieter
1
0
Fork 0
Code Issues 11 Pull Requests Packages Releases Activity

Safe concurrent writes #3

New Issue
Closed
opened 2024-05-30 16:42:04 +02:00 by Jef Roosens · 0 comments
Jef Roosens commented 2024-05-30 16:42:04 +02:00
Owner

It's currently possible to place a repository in a broken state if you simply spam it with multiple uploads at the same time.

To solve this, we need to introduce some formm of concurrency control so packages do not get added simultaneously.

It's currently possible to place a repository in a broken state if you simply spam it with multiple uploads at the same time. To solve this, we need to introduce some formm of concurrency control so packages do not get added simultaneously.
Jef Roosens added this to the 0.1.0 milestone 2024-05-30 16:42:04 +02:00
Jef Roosens added the
bug
 label 2024-05-30 16:42:04 +02:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
feat/mirror-api
dev
fix-ci
agents
concurrent-repos
db-centric-repos
distro
repo-db
main
0.1.0
Labels
Clear labels   
Roadmap
   
bug

Something is not working   
duplicate

This issue or pull request already exists   
enhancement

New feature   
help wanted

Need some help   
idea

Brainstorming issue for a possible new enhancement   
invalid

Something is wrong   
question

More information is needed   
wontfix

This won't be fixed
No Label
Roadmap
bug
duplicate
enhancement
help wanted
idea
invalid
question
wontfix
Milestone
Clear milestone
No items
No Milestone
0.1.0
Assignees
Clear assignees
No Assignees
1 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: Chewing_Bever/rieter#3
There is no content yet.
Delete Branch "%!s(<nil>)"

Deleting a branch is permanent. Although the deleted branch may exist for a short time before cleaning up, in most cases it CANNOT be undone. Continue?