28e681b9df
- ConfigureWireguard and RemoveWireguardPeer mutate the hub too, and were not taking the lock, so a sync could still read the interface around them and write stale state. Both now hold wireguard:hub, which is what makes the read/mutation guarantee actually hold. - The duplicate-key check ran before the allocation lock, so two concurrent creations with the same key both passed it and the loser hit the unique index as an unhandled 500. The check moved inside the lock, with the index kept as a caught backstop for any writer that does not take it — reproduced in a test by inserting a colliding row from within the allocation call. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| Actions | ||
| Console | ||
| Http | ||
| Livewire | ||
| Models | ||
| Notifications | ||
| Providers | ||
| Provisioning | ||
| Services | ||
| Support | ||