Skip to content

merge queue: embarking main (b35651e) and #1315 together#1320

Closed
mergify[bot] wants to merge 3 commits intomainfrom
mergify/merge-queue/8d2d3d1e1e
Closed

merge queue: embarking main (b35651e) and #1315 together#1320
mergify[bot] wants to merge 3 commits intomainfrom
mergify/merge-queue/8d2d3d1e1e

Conversation

@mergify
Copy link
Copy Markdown
Contributor

@mergify mergify Bot commented Apr 30, 2026

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

Branch main (b35651e) and #1315 are embarked together for merge.

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

Required conditions of queue rule default for merge:

Required conditions to stay in the queue:

---
checking_base_sha: b35651ea4cce3ab7ffd3af0ebdae593758837b79
previous_failed_batches: []
pull_requests:
  - number: 1315
    scopes: []
scopes: []
...

jd and others added 3 commits April 29, 2026 14:22
`CommandError.__str__` decoded captured stdout as strict UTF-8, so any
non-UTF-8 bytes from a subprocess (legacy locales, binary diff fragments,
truncated multi-byte sequences) would turn `str(error)` into a
`UnicodeDecodeError`. Every error-formatting site is affected — the
top-level CLI handler in `cli.py:104`, log messages, etc. — converting
the failure into an unhandled traceback instead of a clean message.

Switch to `decode(errors="replace")`. Invalid bytes become the U+FFFD
replacement character; all other formatting is preserved.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Change-Id: I3e3fd853218a6c4294b17e9529794320288124e5
The exception handler around `fetch_old_pr_heads` previously did a
silent `pass`, leaving every revision-history entry stamped
"unknown" with no clue why. When a real failure happens (fork remote
without `refs/pull/N/head`, network error, missing permissions, …)
the user has no signal that anything went wrong — they only see the
symptom in the PR comment days later.

Log the underlying error in orange so the cause is visible at push
time. The exception text is run through `rich.markup.escape` so any
`[`/`]` in the git error message is rendered literally rather than
parsed as Rich markup. Behaviour stays non-fatal: classification
still falls back to "unknown" and the push proceeds.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Change-Id: Id33459ea069be228f73fb02a7f813f16db145b71
@mergify mergify Bot deployed to Mergify Merge Protections April 30, 2026 06:44 Active
@mergify mergify Bot closed this Apr 30, 2026
@mergify mergify Bot deleted the mergify/merge-queue/8d2d3d1e1e branch April 30, 2026 06:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

1 participant