Repository navigation
Remove the mutex usage for Delete GS in both GS and GSS controllers - #572
Conversation
|
Build Succeeded 👏 Build Id: b3f0b98b-5ccc-48cf-a5d2-38d57a466aac The following development artifacts have been built, and will exist for the next 30 days:
A preview of the website (the last 30 builds are retained): To install this version:
|
|
Build Succeeded 👏 Build Id: f39896b7-16b7-4d0c-91fd-21f961c60f53 The following development artifacts have been built, and will exist for the next 30 days:
A preview of the website (the last 30 builds are retained): To install this version:
|
|
Build Succeeded 👏 Build Id: 30d564ee-2ef5-4d05-a61d-9ba0ebe67402 The following development artifacts have been built, and will exist for the next 30 days:
A preview of the website (the last 30 builds are retained): To install this version:
|
|
We need to squash all commits into one, but otherwise LGTM. |
5daf2b6 to
78412ad
Compare
|
Build Succeeded 👏 Build Id: 1d1ca6d4-1f9b-49cc-95ee-4a4e59092b4f The following development artifacts have been built, and will exist for the next 30 days:
A preview of the website (the last 30 builds are retained): To install this version:
|
markmandel
left a comment
There was a problem hiding this comment.
This LGTM as well! Nice work 🌵
AllocationMutex usage is unnecessary for Delete GS since the Shutdown state of GS prevents race conditions. Also remove direct Delete of GS and change it with setting the status of GS to Shutdown and let the GS controller to take care of it.