Possible edit race condition? #30
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
keyop-go/nfq_forwarder#30
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?
It looks to me like there may be a possible race condition if two browser sessions have the 'edit' view open at the same time and attempt to make changes. Investigate this and find a way to resolve it if this turns out to be a valid concern.
changed the description
mentioned in merge request !73
mentioned in commit
8df131d454mentioned in merge request !75
Confirmed this is a real race condition (a classic lost-update: two sessions loading the same config, second save silently overwrites the first with no warning). Implementation up for review: !75 (branch
issue30_config_edit_race_condition) - adds optimistic concurrency control (a content hash issued on read, required back on save, rejected with 409 if the file changed underneath). See the MR description for full detail.mentioned in commit
b09470ea60Merged via !75 (merge commit
b09470e) and released as v1.1.5 (patch bump).