-
Notifications
You must be signed in to change notification settings - Fork 295
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Data race detected in internal/utilization/utilization.go #949
Comments
To ensure that we can verify that the fix we release for this when it's been diagnosed covers your specific case can you provide a testcase which reproduces the problem you are reporting here, in a way that doesn't expose anything proprietary or relies on external components not needed to verify this condition? With a race condition it can be important to know we're trying the same set of call flows that you are when the race condition is occurring. |
Although I haven't been able to reproduce your error, analysis of the code base has identified a potential source for a race condition that could be triggered in some circumstances. I'm putting in a correction for this issue and we'll see if this resolves the problem you're having. |
Thanks. It's hard to provide a simple test case, as the issue was detected on an integration test for a full application. |
I have merged a proposed fix to our |
Fixed in 3.35.0 |
After upgrading to v3.34.0, a data race condition is detected in my tests.
Description
After upgrading from Go 1.22 to Go 1.23 and from NR GoAgent 3.32.0 to 3.34.0, my tests are failing because of the following race condition:
Steps to Reproduce
Tests are run from inside a Docker container.
Expected Behavior
No race condition.
NR Diag results
N/A
Your Environment
N/A
Reproduction case
N/A
Additional context
N/A
The text was updated successfully, but these errors were encountered: