Hypothetical BaseConfigSchema migration race conditions #82
Labels
No labels
bug
duplicate
enhancement
help wanted
invalid
question
wontfix
No milestone
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
cswimr/tidegear#82
Loading…
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?
I've not tested this, but it might be possible for multiple cogs, loading simultaneously, to run migrations at the same time and end up clobbering each other and corrupting the configuration. The simple fix for this is using a lock to ensure that migrations can only be ran once at a time.