From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: pdm-devel@lists.proxmox.com, Lukas Wagner <l.wagner@proxmox.com>
Subject: applied: [PATCH datacenter-manager 2/5] parallel fetcher: make sure to inherit log context
Date: Thu, 5 Feb 2026 19:08:21 +0100 [thread overview]
Message-ID: <177031489314.1855911.2132922520727709653.b4-ty@proxmox.com> (raw)
In-Reply-To: <20260204152723.482258-3-l.wagner@proxmox.com>
On Wed, 04 Feb 2026 16:27:20 +0100, Lukas Wagner wrote:
> If ParallelFetcher is used in a worker task, we need to ensure to
> inherit the log context from the current task, otherwise log messages
> printed in the handler function are not printed to the task log.
>
>
Applied, thanks!
FWIW, shoukd this be a more frequent pattern, we might want to add a
current_scope fn to LogContext that is the same as the scope fn, but
wraps it transparently into a future in the current log context or
the one passed as parameter.
[2/5] parallel fetcher: make sure to inherit log context
commit: c1f3c4a4ad253a1c620941f4bd7eee8ce581ecba
next prev parent reply other threads:[~2026-02-05 18:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-04 15:27 [PATCH datacenter-manager 0/5] improvements for ParallelFetcher Lukas Wagner
2026-02-04 15:27 ` [PATCH datacenter-manager 1/5] parallel fetcher: clean up imports Lukas Wagner
2026-02-05 18:08 ` applied: " Thomas Lamprecht
2026-02-04 15:27 ` [PATCH datacenter-manager 2/5] parallel fetcher: make sure to inherit log context Lukas Wagner
2026-02-05 18:08 ` Thomas Lamprecht [this message]
2026-02-04 15:27 ` [PATCH datacenter-manager 3/5] parallel fetcher: add builder and make struct members private Lukas Wagner
2026-02-05 18:08 ` applied: " Thomas Lamprecht
2026-02-04 15:27 ` [PATCH datacenter-manager 4/5] parallel fetcher: improve result type ergonomics Lukas Wagner
2026-02-05 18:17 ` Thomas Lamprecht
2026-02-04 15:27 ` [PATCH datacenter-manager 5/5] parallel fetcher: add module documentation Lukas Wagner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=177031489314.1855911.2132922520727709653.b4-ty@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=l.wagner@proxmox.com \
--cc=pdm-devel@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox