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
When elliptics log level is changed (for example via dnet_ioclient -r addr:port:family -M debug), it only affects elliptics logger.
And while eblob (lower level library) uses the same blackhole logger, it has internal log-level field, which is never updated after eblob initialization. Eblob's log-level field is being set in dnet_blob_config_init() only. Eblob checks whether current log level allows new message to be printed, and while blackhole would print new message (its log level has changed), it is not called, since eblob's own log level hasn't changed.
There are 2 ways to fix this:
update eblob and never check its internal log-level, it will only exist in ABI as unused field, and all log-level related checks will happen in blackhole logger
propagate log-level changes into eblob internal logger's field, when elliptics' log-level is being changed. This is noticeably simpler solution, although not aesthetically pure.
The text was updated successfully, but these errors were encountered:
When elliptics log level is changed (for example via
dnet_ioclient -r addr:port:family -M debug
), it only affects elliptics logger.And while eblob (lower level library) uses the same blackhole logger, it has internal log-level field, which is never updated after eblob initialization. Eblob's log-level field is being set in
dnet_blob_config_init()
only. Eblob checks whether current log level allows new message to be printed, and while blackhole would print new message (its log level has changed), it is not called, since eblob's own log level hasn't changed.There are 2 ways to fix this:
The text was updated successfully, but these errors were encountered: