Closed pmalek closed 4 months ago
If we're fine with making Config
goroutine safe then I'd be happy to submit a PR to fix this.
That is a perfectly valid thing to do.
cc @vladimirvivien any concerns on doing this?
@pmalek and @harshanarayana I am Ok making this concurrency safe.
I've created https://github.com/kubernetes-sigs/e2e-framework/pull/367 to cover this. There's a question in the PR description whether we'd like to cover all Config
's field or just leave it with client.
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
Will most likely be covered by #396.
/remove-lifecycle stale
What happened?
Data race in
pkg/envconf/config.go
What did you expect to happen?
No data race
How can we reproduce it (as minimally and precisely as possible)?
Anything elese we need to know?
No response
E2E Provider Used
kind
e2e-framework
Versionv0.3.1-0.20231113122213-262cac32d35e
OS version