Skip to content

merge queue: embarking main (e104116) and #622 together#624

Closed
mergify[bot] wants to merge 2 commits intomainfrom
mergify/merge-queue/6fdab54ab2
Closed

merge queue: embarking main (e104116) and #622 together#624
mergify[bot] wants to merge 2 commits intomainfrom
mergify/merge-queue/6fdab54ab2

Conversation

@mergify
Copy link
Contributor

@mergify mergify bot commented Mar 5, 2026

🎉 This pull request has been checked successfully and will be merged soon. 🎉

Branch main (e104116) and #622 are embarked together for merge.

This pull request has been created by Mergify to speculatively check the mergeability of #622.
You don't need to do anything. Mergify will close this pull request automatically when it is complete.

Required conditions of queue default for merge:

No extra conditions.

Required conditions to stay in the queue:

---
checking_base_sha: e1041169ebe9698539770dad5a815ee288a4aef5
previous_failed_batches: []
pull_requests:
  - number: 622
...

jd and others added 2 commits March 3, 2026 20:14
Stop passing `exc_info=` as a kwarg to `logger.log()`. Standard
`logging.Logger` treats this specially (appends traceback), but loguru
interprets all kwargs as message format parameters, causing a KeyError.

Instead, format the traceback into the message string directly using
`traceback.format_exception()`. This works with all loggers that
implement `LoggerProtocol` (logging, loguru, structlog, etc.).

Also tighten `LoggerProtocol.log()` by removing `**kwargs` since we
no longer pass any keyword arguments.

Fixes #420

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Change-Id: Icc145539d443c83f09266e25b9819bd2516aeddc
@mergify mergify bot closed this Mar 5, 2026
@mergify mergify bot deleted the mergify/merge-queue/6fdab54ab2 branch March 5, 2026 07:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant