Handle concurrent manipulation of suggestions and drafts #439
Labels
No labels
automation
backend
bug
contributor experience
data
deployment
documentation
duplicate
good first issue
help wanted
nice to have
notifications
package maintainer
performance
skin
tech debt
user story
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: lix-community/nix-security-tracker#439
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
There are denerate cases (which become more likely with more users of the service) where multiple people add or remove entries form the suggestion list or add/remove packages from a suggestion/draft. Right now there's no way for an individual user to notice that this is happening, and after reloading the resulting state will be surprising because it's inconsistent with perceived interactions.
In particular in the activity log we should neatly summarise the case where multiple people concurrently do and undo removals or status changes.