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 am using Gitlab as unleash API, and I came across an error, where a request for an API-call against my microservice was timed out, since it never leaves the isEnabled func. After debugging I found out, that the metrics count in the defer is blocking infinitely. https://github.com/Unleash/unleash-client-go/blob/v3/client.go#L243
Further it was really hard to figure this out as it is in the defer. I know, that I can disable the metrics, and that`s my fix for it, but imho this should not block. It should return an error instead or panic, but it was really hard to figure this out.
Steps to reproduce the bug
No response
Expected behavior
No blocking
Logs, error output, etc.
No response
Screenshots
No response
Additional context
No response
Unleash version
3.8.0
Subscription type
None
Hosting type
None
SDK information (language and version)
Go
The text was updated successfully, but these errors were encountered:
Hello again @c0olix. We have reproduced this issue and are working on a fix. The issue is due to messaging blocking when no listeners have been configured. So in the meantime until we can get a fix out a workaround is to include the unleash.WithListener(&unleash.DebugListener{}), in the unleash initialization
Describe the bug
I am using Gitlab as unleash API, and I came across an error, where a request for an API-call against my microservice was timed out, since it never leaves the isEnabled func. After debugging I found out, that the metrics count in the defer is blocking infinitely.
https://github.com/Unleash/unleash-client-go/blob/v3/client.go#L243
Further it was really hard to figure this out as it is in the defer. I know, that I can disable the metrics, and that`s my fix for it, but imho this should not block. It should return an error instead or panic, but it was really hard to figure this out.
Steps to reproduce the bug
No response
Expected behavior
No blocking
Logs, error output, etc.
No response
Screenshots
No response
Additional context
No response
Unleash version
3.8.0
Subscription type
None
Hosting type
None
SDK information (language and version)
Go
The text was updated successfully, but these errors were encountered: