fix: lock adding to tailnet waitgroup to avoid race (and fix flake) #14195
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.
Fixes #14143.
Fixes a race condition that can occur when a
tailnet
connection is closed just before a network telemetry event is about to be sent off. Specifically, wherewaitgroup.Add(n)
is called on a waitgroup wherewaitgroup.Wait()
is currently blocking another goroutine.This works as we only call
Wait()
on thetelemetryWg
waitgroup when theConn
mutex is held, and only after the closed channel has been closed. We then require that the goroutine sending the telemetry event acquire said mutex, and that the channel is not closed, before adding to the waitgroup and sending the event.