cmd/faucet: fix websocket race regression after switching to gorilla #22136
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
About a year ago we switched over the websocket library in the faucet from Go's implementation to the Gorilla library. Unfortunately the former was thread safe whilst the latter was not, and we didn't update the faucet code to add mutexes. This was undetected for quite a long time since our faucet auto-restarts, so an occasional crash was just silently ignored.
Fixes