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
{{ message }}
This repository has been archived by the owner on Nov 23, 2020. It is now read-only.
I'm attempting to use Pulsar to rewire a legacy synchronous system in the actor style. I have pre-existing logging configurations that I would prefer to use (multiple file handlers for different subpackages/modules).
I tried setting cfg.set('log_handlers', logging._handlerList), but that fails when it runs dictConfig in log.configuredLogger because I've already called dictConfig prior to setting up the Pulsar arbiter. ValueError: Unable to configure root logger: Unable to add handler <weakref at 0x10c892408; to 'FileHandler' at 0x10c89eac8>
Even that was a bit of a shot in the dark. I couldn't find a clear way to disable the logging autoconfig and control the config myself.
Expected behaviour
Ability to use Pulsar as a library which allows me to define my own logging config.
Actual behaviour
Pulsar configures logging itself, overriding logging config that I have setup.
Steps to reproduce
Setup logging using dictConfig.
Initialize an arbiter.
Original logging config is overwritten when self.cfg.configured_logger is called in Concurrency.get_event_loop()
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Description
I'm attempting to use Pulsar to rewire a legacy synchronous system in the actor style. I have pre-existing logging configurations that I would prefer to use (multiple file handlers for different subpackages/modules).
I tried setting
cfg.set('log_handlers', logging._handlerList)
, but that fails when it runsdictConfig
inlog.configuredLogger
because I've already calleddictConfig
prior to setting up the Pulsar arbiter.ValueError: Unable to configure root logger: Unable to add handler <weakref at 0x10c892408; to 'FileHandler' at 0x10c89eac8>
Even that was a bit of a shot in the dark. I couldn't find a clear way to disable the logging autoconfig and control the config myself.
Expected behaviour
Ability to use Pulsar as a library which allows me to define my own logging config.
Actual behaviour
Pulsar configures logging itself, overriding logging config that I have setup.
Steps to reproduce
dictConfig
.self.cfg.configured_logger
is called inConcurrency.get_event_loop()
The text was updated successfully, but these errors were encountered: