You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi @DavidS-om, thank you. Just confirming that we're aware of some issues with data races (and issues running our unit tests with the -race flag enabled) and it's on our radar.
@StephenCathcart thanks for the message. As I wrote above, for now we've pinned to v5.11.0 and are not experiencing the issue, so it's not a burning issue. It only means that we're stuck on that version until this is fixed as updating completely breaks our internal testing.
Steps to reproduce
Expected behavior
driver does not trigger data races when running under
go test -race
Actual behavior
we see regular (>50% of
go test -race
runs) data races in the neo4j driver connection shutdown code:The issue goes away when downgrading to v5.11.0.
The text was updated successfully, but these errors were encountered: