fix_tractor_logging: porting to latest tractor.log API(s) #76
Loading…
Reference in New Issue
There is no content yet.
Delete Branch "fix_tractor_logging"
Deleting a branch is permanent. Although the deleted branch may exist for a short time before cleaning up, in most cases it CANNOT be undone. Continue?
Repeat of #74, bc apparently i’m real bad a adjusting the base branch..
Below is copied verbatim from there..
Like it sounds, adjusting to the new
tractor.log.get_logger()/.get_consolelog()semantics itro-ed in,https://github.com/goodboy/tractor/pull/402
Summary of changes,
.get_logger()calls to passname=__name__at the module level.get_logger()setup in pkg-modules (eg.piker.brokers.__init__) and instead calling in every lead-submod to ensure msg headers reflect each file which emits a message.logleveldown from the UI-app (normallypiker chart) to all requested subsystems so they reflect the CLI-flag level provided by the user on the console.piker.log.get_console_log()/.get_logger()to route nicely to the underlyingtractor.log.get_console_log()call given our usage inpiker.piker.piker.kinda thing.tractorinternal-logging is configured appropriately based on user input via--tl <level>from various CLI endpoints.Kinda unrelated tweaks also added here,
Cursor.is_hovered()predicate.print()s relateed to ^ to equiv logger calls.platformdirsdep to latest release version.fix_tractor_loggingto fix_tractor_logging: porting to latest `tractor.log` API(s)