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
I have several tests with a similar setup: the provider is created, then configured, the tests are executed, and openfeature.Shutdown() is called for cleanup. However, when these tests are run with the race detector enabled, they consistently fail.
@beeme1mr I am trying to implement the provider and write some e2e tests for it. Using another provider doesn't help much. The issue is related to the providers which implement StateHandler interface.
There have been substantial changes to the SDK recently like @beeme1mr said, which are yet unreleased.
The changes are significant enough that there's a chance this bug could be resolved. I would have liked to see the released already but there's a few more issues we have to iron out with it, namely the one you pointed out here: #296 (review)
Observed behavior
I have several tests with a similar setup: the provider is created, then configured, the tests are executed, and
openfeature.Shutdown()
is called for cleanup. However, when these tests are run with the race detector enabled, they consistently fail.Expected Behavior
No response
Steps to reproduce
Create a file with test and run
go test -race ./...
The text was updated successfully, but these errors were encountered: