[Bugfix] Accessing channel without protection

I was accessing a lock-protected channel without holding the lock. That
definitely seems to defeat the purpose of having the lock in the first
place.

Signed-off-by: Will Hawkins <[email protected]>

1 files changed, 7 insertions, 3 deletions

diff --git a/rpm/rpm.go b/rpm/rpm.go
index 95e6192..d1c07a5 100644
--- a/rpm/rpm.go
+++ b/rpm/rpm.go
@@ -150,10 +150,14 @@ func ResponsivenessProber[BucketType utilities.Number](
 
 				currentBucketId := bucketGenerator.Generate()
 
-				dataPoints <- series.SeriesMessage[ResponsivenessProbeResult, BucketType]{
-					Type: series.SeriesMessageReserve, Bucket: currentBucketId,
-					Measure: utilities.None[ResponsivenessProbeResult](),
+				dataPointsLock.Lock()
+				if dataPoints != nil {
+					dataPoints <- series.SeriesMessage[ResponsivenessProbeResult, BucketType]{
+						Type: series.SeriesMessageReserve, Bucket: currentBucketId,
+						Measure: utilities.None[ResponsivenessProbeResult](),
+					}
 				}
+				dataPointsLock.Unlock()
 
 				// The presence of a custom TLSClientConfig in a *generic* `transport`
 				// means that go will default to HTTP/1.1 and cowardly avoid HTTP/2: