TLDR Tech / Practical
Go's race detector: harmless warning vs silent corruption
A technical analysis explains how Go's race detector can flag issues when concurrent reads of HTTP request bodies occur due to internal transport reusing global buffers for retries. The author illustrates that reusing shared byte buffers can lead to mixed data if a server replies before the request is fully transmitted. Two scenarios are presented: vmagent, where the race was deemed inconsequential as leftover data wasn't read, and vmauth, where a shared cursor caused undetected request corruption requiring a correction.
Read the full story