feat(logging): central taskito logger with AM/PM timestamps#155
Merged
Conversation
pyo3-log forwards Rust log::* records into Python's logging module. Activated lazily via _init_rust_logging() so cold imports don't deadlock against r2d2 pool builders, and PyQueue::new releases the GIL during storage init so connection-pool worker threads can flush log records.
One configure() call attaches a single managed handler to the taskito Python logger and the four taskito_* loggers populated by pyo3-log. The default format keeps today's [ts] LEVEL message shape; the timestamp gains AM/PM via %I:%M:%S %p. Idempotent and thread-safe. Wired into the CLI entry and run_worker so every 'app runs' path uses the same sink. configure_logging is exported from the package for embedded users (Django/FastAPI) to call themselves.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
One canonical entry point — `taskito.configure_logging()` — that owns the `taskito` logger and bridges Rust `log::*` records into the same sink. Used by every CLI subcommand and `Queue.run_worker` so all 'app runs' paths share one format and one destination.
Sample output
```
[2026-05-08 04:08:18 PM] INFO smoke message from python
[2026-05-08 04:08:18 PM] INFO smoke from sub-logger
```
Test plan