-
Notifications
You must be signed in to change notification settings - Fork 19
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
[BUG] Api.Shutdown()
hangs on reuse
#186
Labels
bug
Something isn't working
Comments
Ah, okay, its blocking on the bounded channel inside of |
austindrenski
added a commit
to austindrenski/open-feature-dotnet-sdk
that referenced
this issue
Jan 17, 2024
Previously, we shutdown the consumer thread causing any reuse of the Api to block on the second event emitted to the event executor. Fixes: open-feature#186 Signed-off-by: Austin Drenski <[email protected]>
austindrenski
added a commit
to austindrenski/open-feature-dotnet-sdk
that referenced
this issue
Jan 17, 2024
Previously, we shutdown the consumer thread causing any reuse of the Api to block on the second event emitted to the event executor. Fixes: open-feature#186 Signed-off-by: Austin Drenski <[email protected]>
austindrenski
added a commit
to austindrenski/open-feature-dotnet-sdk
that referenced
this issue
Jan 17, 2024
Previously, we shutdown the consumer thread causing any reuse of the Api to block on the second event emitted to the event executor. Fixes: open-feature#186 Signed-off-by: Austin Drenski <[email protected]>
austindrenski
added a commit
to austindrenski/open-feature-dotnet-sdk
that referenced
this issue
Jan 18, 2024
Previously, we shutdown the consumer thread causing any reuse of the Api to block on the second event emitted to the event executor. Fixes: open-feature#186 Signed-off-by: Austin Drenski <[email protected]>
austindrenski
added a commit
to austindrenski/open-feature-dotnet-sdk
that referenced
this issue
Jan 19, 2024
Previously, we shutdown the consumer thread causing any reuse of the Api to block on the second event emitted to the event executor. Fixes: open-feature#186 Signed-off-by: Austin Drenski <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Observed behavior
Stumbled onto this while investigating failing unit tests add as part of #181 that fail when run in concert, but pass when run independently.
Working theory is that we're not restarting the consumer thread. Patch forthcoming.
See: #181
Expected Behavior
No response
Steps to reproduce
No response
The text was updated successfully, but these errors were encountered: