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
Right now if nothing is passed to the LoggingHandler (like in my code above), it can default to the ProxyLoggerProvider which is an API LoggerProvider and it causes that endless recursive call..
Also LoggingHandler expects it’s provider to provide a resource here, which the API LoggerProvider does not have..
Aaron also mentioned that he ran into this and can probably provide more context on what exactly the issues are here and how to fix things
Steps to Reproduce
See above..
Expected Result
See above.
Actual Result
See above..
Additional context
No response
Would you like to implement a fix?
Yes
The text was updated successfully, but these errors were encountered:
Right now if nothing is passed to the LoggingHandler (like in my code above), it can default to the ProxyLoggerProvider which is an API LoggerProvider and it causes that endless recursive call..
I think it does assume this right now but it should not. Also see #4330
Also LoggingHandler expects it’s provider to provide a resource here, which the API LoggerProvider does not have..
I think the underlying problem is that the LogRecord API should not have a resource. (the exporting format that is part of LogData is something different)
Describe your environment
No response
What happened?
The SDK
LoggingHandler
can be initialized in a bad state by doing justhandler = LoggingHandler()
.When i do this:
We end up in an endless recursive loop here and the program crashes.
It seems
LoggingHandler
should require that a SDKLoggerProvider
is passed in, and not an APILoggerProvider
. ?Right now if nothing is passed to the
LoggingHandler
(like in my code above), it can default to theProxyLoggerProvider
which is an API LoggerProvider and it causes that endless recursive call..Also
LoggingHandler
expects it’s provider to provide a resource here, which the API LoggerProvider does not have..Aaron also mentioned that he ran into this and can probably provide more context on what exactly the issues are here and how to fix things
Steps to Reproduce
See above..
Expected Result
See above.
Actual Result
See above..
Additional context
No response
Would you like to implement a fix?
Yes
The text was updated successfully, but these errors were encountered: