fix_tractor_logging: porting to latest tractor.log API(s) #74

goodboy · 2026-02-23T03:17:59Z

goodboy commented

2026-02-23 03:17:59 +00:00

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,

adjusting all .get_logger() calls to pass name=__name__ at the module level.
generally dropping all subsys-common 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.
ensuring we pass loglevel down from the UI-app (normally piker chart) to all requested subsystems so they reflect the CLI-flag level provided by the user on the console.
reworking piker.log.get_console_log()/.get_logger() to route nicely to the underlying tractor.log.get_console_log() call given our usage in piker.
- mostly ensuring we don’t double-tag-headers with piker.piker. kinda thing.
- ensuring that tractor internal-logging is configured appropriately based on user input via --tl <level> from various CLI endpoints.
various doc-string additions (kinda randomly) where i felt appropriate while conducting this patch.
like always, type-annot and general code re-styling.

Kinda unrelated tweaks also added here,

add a Cursor.is_hovered() predicate.
add a warning log when the user mouse-over-cancels an order but the order_mode api reports none were cancelled (according to emsd’s resonse).
generally converting any print()s relateed to ^ to equiv logger calls.
bumping platformdirs dep to latest release version.

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, - adjusting all `.get_logger()` calls to pass `name=__name__` at the module level. - generally dropping all subsys-common `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. - ensuring we pass `loglevel` down from the UI-app (normally `piker chart`) to all requested subsystems so they reflect the CLI-flag level provided by the user on the console. - reworking `piker.log.get_console_log()/.get_logger()` to route nicely to the underlying `tractor.log.get_console_log()` call given our usage in `piker`. * mostly ensuring we don't double-tag-headers with `piker.piker.` kinda thing. * ensuring that `tractor` internal-logging is configured appropriately based on user input via `--tl <level>` from various CLI endpoints. - various doc-string additions (kinda randomly) where i felt appropriate while conducting this patch. - like always, type-annot and general code re-styling. Kinda unrelated tweaks also added here, - add a `Cursor.is_hovered()` predicate. - add a warning log when the user mouse-over-cancels an order but the order_mode api reports none were cancelled (according to emsd's resonse). - generally converting any `print()`s relateed to ^ to equiv logger calls. - bumping `platformdirs` dep to latest release version.

goodboy added 18 commits 2026-02-23 03:17:59 +00:00

f116d1a03b Adjust `tractor.log` API compat

Update logging helpers to use new `tractor.log` API with `pkg_name=`
kwarg and add optional `tractor` "root logger" enabling.

Deats,
- change `piker.log.get_logger()` to use `pkg_name=` vs `_root_name=`.
- add `**tractor_log_kwargs` passthrough to both wrapper fns.
- add `with_tractor_log: bool` toggle to `.get_console_log()`.
- strip `'piker.'` prefix from logger names when present to avoid
  newly added `tractor.get_logger()` warnings.

Surroundingly,
- add `subsys` import to `.clearing._ems` for log name
- update all `get_console_log()` calls to use `level=` kwarg
- add assertion checks for logger names in `_setup_persistent_emsd()`

Additionally,,
- fix all type annotations: `str|None` vs `str | None`.
- add multiline style to conditional in `.cli.services()`.
- drop unused `Optional` import from `._actor_runtime`.
- drop a few "blank lines" in various function sigs.

Warning: this patch will require an equivalent dev-commit at the time of
writing in `tractor` itself, for now the `piker_pin` branch should be
sufficient to avoid breakage 🙏!

(this commit msg was generated in some part by [`claude-code`][claude-code-gh])
[claude-code-gh]: https://github.com/anthropics/claude-code

k

0dc6af3c1e Bump to latest `xonsh` release

81f770bb22 Auto-enable `tractor` logging when runtime active

Check for active `tractor` runtime via `.current_actor()` and use its
`.loglevel` to auto-enable `tractor`'s internal console logging when
`with_tractor_log` is not explicitly set.

Deats,
- add `tll` (tractor log level) var to capture level
- check `with_tractor_log is not False` first
- fallback to `maybe_actor.loglevel` if runtime exists
- only call `tractor.log.get_console_log()` if `tll` set
- add TODO comment about "log-spec" style config support

(this commit msg was generated in some part by [`claude-code`][claude-code-gh])
[claude-code-gh]: https://github.com/anthropics/claude-code

2e31ecbbe7 .brokers._daemon: enable `tractor` log in `brokerd`

Also,
- capture `Actor.loglevel` in `tll` var for reuse (when `loglevel` is
  null) and pass `bool`-ed as new `with_tractor_log`-flag.
- add `with_tractor_log=bool(tll)` to `.get_console_log()`
- add assertion check for logger name.
- comment-out `tractor.trionics.collapse_eg()` context for now, pretty
  sure we don't need it and it just ends up adding extra logging
  overhead for no good reason (warnings on various `trio` internal
  cancelled-maskings, etc).
- change type annotation: `str|None` vs `str | None`.

(this commit msg was generated in some part by [`claude-code`][claude-code-gh])
[claude-code-gh]: https://github.com/anthropics/claude-code

76eefb97e2 .ui._app: enable console logging in `_async_main()`

Now we're actualy emitting colored-logs (again?), not sure how this got
borked but maybe it's due to `tractor.log`'s new changes?

(this commit msg was generated in some part by [`claude-code`][claude-code-gh])
[claude-code-gh]: https://github.com/anthropics/claude-code

e5b9fe97b4 Add order-cancel debugging and multiline kbd logs

Add verbose logging + error handling for order cancellation
hotkey path and multiline style for view-mode kb msgs.

Deats,
- add `Cursor.is_hovered()` to check hover state
- log warnings when no orders cancelled via <c> hotkey
- add try-except around `.cancel_orders_under_cursor()`
- log `cur._hovered` state in `.ui._lines` hover handlers
- change `Dialog.cancel_orders()` to return `list[Dialog]`
- fix import: `Flume` from `.data.flows` vs `.data.feed`
- comment-out multi-status msgs in order submit/cancel

Also,
- convert all multiline kbd `if` conditionals to use `and`
  on separate lines for consistency
- move `import tractor` to top of `._interaction`
- change `print()` to `log.debug()` in `LevelLine`
- fix type annotation spacing: `Callable|None` vs `Callable | None`

(this commit msg was generated in some part by [`claude-code`][claude-code-gh])
[claude-code-gh]: https://github.com/anthropics/claude-code

52c1c9c0fd .fsp._engine: enable console logging in `cascade()`

Add console log setup with module name + multiline style for
desync warning msg.

Also,
- fix import: `Flume` from `.data.flows` vs `.data.feed`
- move `Feed` to `TYPE_CHECKING` block
- add TODO comment about `tractor._state` dict issue

(this commit msg was generated in some part by [`claude-code`][claude-code-gh])
[claude-code-gh]: https://github.com/anthropics/claude-code

13edd7f709 .data.feed: move `Flume` import to avoid cycle

Move `Flume` to `TYPE_CHECKING` and add runtime imports in
`allocate_persistent_feed()` + `open_feed()` to avoid cycle
with `.flows` mod.

(this commit msg was generated in some part by [`claude-code`][claude-code-gh])
[claude-code-gh]: https://github.com/anthropics/claude-code

b0ac3cd9b0 Use `__name__` for loggers across `.ib` sub-mods

Change all `.ib` sub-modules to use `get_logger(name=__name__)`
for per-module logger instances vs shared `._util.log`.

Deats,
- change `._util` to use `__name__` vs literal string.
- change `.broker`, `.feed`, `.ledger`, `.symbols` to import
  `get_logger()` from top-level `.log` and call with `__name__`.
- drop `log` imports from `._util` in all affected mods.

Also,
- drop trailing comma in `.cli.services()` conditional for `loglevel`
  passthrough -> fixes an actual kwargs bug!!

(this commit msg was generated in some part by [`claude-code`][claude-code-gh])
[claude-code-gh]: https://github.com/anthropics/claude-code

041f0d7e6f Use `__name__` for loggers across most sub-mods

Change most sub-modules to use `get_logger(name=__name__)` for
per-leaf-module `log` instances vs previous subpkg-level/shared refs.

Primary changes,
- import `get_[console_]logger()` from top-level `piker.log` across leaf
  mods.
- change any `<subsys>._util.log` logger-instances as well (though this
  approach should no longer be used since it masks the endpoint module's
  emissions.

Also,
- add a defaulted `loglevel: str` param to all `open_trade_dialog()`
  endpoints, anticipating it being passed in by `.clearing`-engine.
- call `get_console_log(level=loglevel, name=__name__)` in each trade
  dialog ep to enable per-`brokerd`-backend console writing.
- drop `get_logger` from `.brokers.__all__` exports
- fix type annotations: `str|None` vs `str | None`
- add TODOs for,
  * comments in `._util` about multi-subsys logging
  * `.accounting.__init__` about console log setup

(this commit msg was generated in some part by [`claude-code`][claude-code-gh])
[claude-code-gh]: https://github.com/anthropics/claude-code

e08fb267f8 Enable console via `.clearing._ems.open_brokerd_dialog()`

Enable console logs for both `.clearing` and `.accounting` in
`open_brokerd_dialog()` and pass `loglevel` to all broker-backend
trade-dialog endpoints. This ensures all `open_trade_dialog()` will
receive the same level passed to the EMS, including the paper engine.

Deats,
- add `loglevel` param to `mk_paper_ep()` closure.
- pass `loglevel=loglevel` to all trade endpoint `open_context()`
  calls and `mk_paper_ep()` invocations.
- change default `loglevel` in `open_ems()` from `'error'` to
  `'warning'`.
- add `get_console_log()` calls for `'clearing'` and
  `'piker.accounting'` at top of `open_brokerd_dialog()` to ensure those
  dependent subsystems are console enabled given they're namely used by
  the `brokerd` trade-dialog ep tasks.

(this commit msg was generated in some part by [`claude-code`][claude-code-gh])
[claude-code-gh]: https://github.com/anthropics/claude-code

e01ba6e31e Pass `loglevel` down through `.data` callstack

Add `loglevel` param propagation across the data feed and sampling
subsystems to enable proper console log setup in downstream (distibuted)
subactor tasks. This ensures sampler and history-mgmt tasks receive the
same loglevel as their parent `.data.feed` tasks.

Deats,
- add `loglevel: str|None` param to `register_with_sampler()`,
  `maybe_open_samplerd()`, and `open_sample_stream()`.
- pass `loglevel` through to `get_console_log()` in
  `register_with_sampler()` with fallback to actor `loglevel`.
- use `partial()` in `allocate_persistent_feed()` to pass
  `loglevel` to `manage_history()` at task-start.
- add `loglevel` param to `manage_history()` with default
  `'warning'` and pass through to `open_sample_stream()` from there.
- capture `loglevel` var in `brokers.cli.search()` and pass to
  `symbol_search()` call.

Also,
- drop blank lines in fn sigs for consistency with piker style.
- add debug bp in `open_feed()` when `loglevel != 'info'`.

(this commit msg was generated in some part by [`claude-code`][claude-code-gh])
[claude-code-gh]: https://github.com/anthropics/claude-code

f2f696d341 Pass `loglevel` to `cascade()` feed/sampler opens

Add `loglevel` param to both `maybe_open_feed()` and
`open_sample_stream()` calls in FSP engine's `cascade()` task to
ensure proper console log setup in downstream sampling tasks.

Deats,
- pass `loglevel=loglevel` to `maybe_open_feed()` call.
- pass `loglevel=loglevel` to `open_sample_stream()` call.

Also,
- switch to explicit kwargs: `fqmes=[fqme]` and `period_s=` for
  clarity and consistency with other callsites.

(this commit msg was generated in some part by [`claude-code`][claude-code-gh])
[claude-code-gh]: https://github.com/anthropics/claude-code

ed58ae139f Pass `loglevel` down through `.ui` graphics tasks

Add `loglevel` propagation to UI graphics tasks and sampler stream
opens to enable proper console logging in chart update loops. This
ensures the graphics and FSP subsystems receive the same loglevel
as their parent and/or sibling UI-actor tasks.

Deats,
- add `loglevel` param to `graphics_update_loop()` and
  `increment_history_view()` with default `'warning'`.
- pass `loglevel` to `open_sample_stream()` calls in both fns.
- use `partial()` to pass `loglevel` through to `nurse.start_soon()`
  calls in `display_symbol_data()` and `graphics_update_loop()`.

Also logging, doc-strs, and code-style tweaks,
- change `print()` -> `log.debug()` for hidden-chart and
  interaction-pause msgs in graphics loop.
- change `log.info()` -> `log.debug()` for resize events in
  `GodWidget` and `MainWindow`.
- add multiline style to resize log msg in `GodWidget`.
- add docstring to `MainWindow.on_focus_change()`.
- moar union type annot adjustments.
- switch to explicit kwarg `period_s=` for `open_sample_stream()`
  in `increment_history_view()`.
- multiline style for `names` list in `open_fsp_actor_cluster()`.
- change `count=2` -> `count=len(names)` in
  `open_fsp_actor_cluster()`.
- add TODO about using `.experimental` for cluster import (once that
  get's patched into upstream `tractor`).
- multiline style for `or` in `FspAdmin.start_engine_task()`.
- comment-out unused `brokernames` in `ui.cli.chart()`.
- add commented breakpoint in `ui.cli.chart()`.
- fix docstring style in `OrderMode.on_submit()`.

(this commit msg was generated in some part by [`claude-code`][claude-code-gh])
[claude-code-gh]: https://github.com/anthropics/claude-code

7c8baa8f4e Use `name=__name__` for logs throughout `.service`

Change all `.service` sub-modules to use `get_logger(name=__name__)`
for per-submod instances vs a shared `._util.log`.

Deats,
- import `get_logger()` and `get_console_log()` from top-level
  `piker.log` instead of `._util` for all.
- drop `log` and `get_console_log()` partial from `._util`.
- add `name=subsys` kwarg to `get_console_log()` call in
  `_actor_runtime.maybe_open_pikerd()`.
- add `name='piker.service'` to `get_console_log()` in
  `_ahab.open_ahabd()`.
- change default `loglevel` from `None` to `'cancel'` in
  `_ahab.open_ahabd()`.
- add sanity check: `assert log.name == 'piker.service'` in
  `_daemon.maybe_spawn_daemon()`.
- change `print()` -> `log.info()` in `_registry.find_service()`.
- drop stray `from piker.service._util import log` import in
  `brokers._daemon.spawn_brokerd()`.

Styling/cleanups,
- drop blank lines from various fn sigs.
- do more sin-ws union type annots.
- add more multiline style to `or` expressions in `_actor_runtime` and
  `_registry`.
- update `._util` docstring with TODO about `import`-time console
  log setup.
- add TODO comments in `_registry` about UDS registry support.
- use `.aid.uid` from actor in `_registry.open_registry()`.
- add intermediate var `reg_addrs` in `_registry.open_registry()` (bc
  i was tracing rtvs value issues in `tractor`).
- add `pformat` import to `.elastic` (code path is currently
  not used but figured might as well appease the linter..)

(this commit msg was generated in some part by [`claude-code`][claude-code-gh])
[claude-code-gh]: https://github.com/anthropics/claude-code

19d647f574 Enable console logging in `.accounting` on import

Enable `get_console_log()` at `.accounting.__init__` import-time
to ensure console output is available whenever the subsystem is
used by `.clearing` or other code.

Deats,
- uncomment and complete `get_console_log()` call in
  `.accounting.__init__` with default `level='warning'` and
  `name=__name__`.
- update comment explaining rationale: better to enable on import
  since namely used by `.clearing` subsystem.

Also,
- change `piker.calc` import to relative `.calc` in
  `.accounting.__init__`.
- drop unused `get_console_log` import from `.accounting._pos`.
- add `log = get_logger(name=__name__)` to `.accounting.cli`.
- change `get_logger(loglevel)` -> `get_console_log()` in
  `.accounting.cli.sync()` with proper kwargs.
- add `get_console_log` import to `.accounting.cli`.

(this commit msg was generated in some part by [`claude-code`][claude-code-gh])
[claude-code-gh]: https://github.com/anthropics/claude-code

1827cdcf0f Bump `platformdirs` version in lock file

70b663992c Better doc-strings n styling in `piker.cli` eps

Add comprehensive docstrings to the top-level CLI endpoints and helpers,
explaining the purpose and structure of each (sub)command.

Deats,
- add detailed docstring to `pikerd()` explaining its role as the
  root service-actor/daemon supervisor.
- add docstring to `cli()` noting it's the root endpoint generally
  requiring a sub-cmd input.
- add extensive docstring to `services()` explaining the daemon naming
  conventions and listing a few current/common service actors.
- add docstring to `_load_clis()` explaining dynamic CLI loading.

Stylin,
- add multiline style to `and not maddrs` conditional in
  `load_trans_eps()`.
- drop commented-out `--tsdb` and `--es` click options from
  `pikerd()`, they're more or less obsolete given `nativedb`.
- add type annots where obviously handy.
- add TODO comment about UDS support in `services()`.

(this commit msg was generated in some part by [`claude-code`][claude-code-gh])
[claude-code-gh]: https://github.com/anthropics/claude-code

goodboy reviewed 2026-02-23 03:32:06 +00:00

piker/data/feed.py Outdated

													
				@ -879,9 +890,12 @@ async def open_feed(

				        providers.setdefault(mod, []).append(bs_fqme)

				        feed.mods[mod.name] = mod

				    if (

goodboy commented

2026-02-23 03:32:06 +00:00

Poster

Lel, right should prolly rm all these trace branches i added while trying to figure out why loglevel wasn’t being passed down through certain layers correctly!

Lel, right should prolly rm all these trace branches i added while trying to figure out why `loglevel` wasn't being passed down through certain layers correctly!

goodboy commented

2026-02-23 18:35:23 +00:00

Poster

Removed em all in latest commit.

goodboy reviewed 2026-02-23 03:33:12 +00:00

piker/log.py

													
				@ -50,4 +62,4 @@

				    )

				def get_console_log(

goodboy commented

2026-02-23 03:33:12 +00:00

Poster

Note the changes here to handle re-routing to tractor.log.get_console_log() appropriately given use throughout piker.

Note the changes here to handle re-routing to `tractor.log.get_console_log()` appropriately given use throughout `piker`.

goodboy force-pushed fix_tractor_logging from 70b663992c to d0add050b7

2026-02-23 17:26:41 +00:00

Compare

goodboy added 1 commit 2026-02-23 18:26:56 +00:00

2d0005ce48 Drop info-level `.pause()`-es used while devving

goodboy reviewed 2026-02-23 18:33:06 +00:00

piker/ui/_interaction.py

													
				@ -247,2 +269,3 @@

				                order_mode.cancel_orders_under_cursor()

				                if not dialogs:

				                    log.warning(

goodboy commented

2026-02-23 18:33:06 +00:00

Poster

This was originally bc i couldn’t figure out why on sway i couldn’t mouse-over-c-cancel orders XD

Turns out it was bc i had keyboard-disabled-while-typing set.

Ideally we can somehow detect this kinda thing more fancy like in the longer term. I just haven’t dug into it yet..

This was originally bc i couldn't figure out why on `sway` i couldn't mouse-over-`c`-cancel orders XD Turns out it was bc i had keyboard-disabled-while-typing set. Ideally we can somehow detect this kinda thing more fancy like in the longer term. I just haven't dug into it yet..

goodboy reviewed 2026-02-23 18:34:15 +00:00

piker/ui/order_mode.py

													
				@ -697,3 +695,1 @@

				            final_msg=f'cancelled orders:\n{oids}',

				            group_key=True

				        )

				        # key = self.multistatus.open_status(

goodboy commented

2026-02-23 18:34:15 +00:00

Poster

Oh yeah right, and i disabled all these “status” things bc they never seem to clear from the bottom of the main widget/window..

will try to see how we can do em better in the future.

Oh yeah right, and i disabled all these "status" things bc they never seem to clear from the bottom of the main widget/window.. will try to see how we can do em better in the future.