Open cyrilc-pro opened 3 weeks ago
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. Thanks.
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 develop
branch which is where our code gets staged shortly before release. Could you try pulling a copy of the agent from that branch and try compiling with that to see if that solves your issue?
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