-
Notifications
You must be signed in to change notification settings - Fork 22
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
LogHandler is shared between multiple AblyRealtime instances #1250
Comments
➤ Automation for Jira commented: The link to the corresponding Jira issue is https://ably.atlassian.net/browse/SDK-3770 |
@palashjhabak let me check on this |
@palashjhabak I have created a PR to fix this issue, we should have the fix merged by tomorrow 👍 |
For the time being, you can pass additional clientOption ->
|
I think Logger is set to internal in the ClientOption class |
Yeah, I think the fix should be available once we merge the PR 👍 |
Perfect. Appreciate your quick response and even quicker PR. Thanks a lot. Cheers. |
I think if I am implementing a custom logging handler, I might want to have AblyRealtime instance-specific things that I would want to log using the custom log handler.
Currenlty since the AblyRealtime is instantiated with a static DefaultLogger Handler, and even if I set a custom loghandler instance through client option, it does not set the Logger property to the custom instance, but it sets the property Logger.Loggersink to the handler, which makes the LoggerSink to be the last set logger sink for all the AblyRealTime instance.
ably-dotnet/src/IO.Ably.Shared/AblyRealtime.cs
Line 63 in d7abbde
┆Issue is synchronized with this Jira Task by Unito
The text was updated successfully, but these errors were encountered: