CLI 0.162.0 panics at terminal_hyperlinks.rs:392: UTF-8 boundary inside ➡ while rendering Chinese text

Chiusa
  • Qualcosa non va?
#52,375 2 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
3/5
Tempo stimato
1-2 giorni
Idoneità per principianti
45/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
rust
Ambito
cli

Direzione di ricerca

Start at remap_source_wrapped_line in codex-rs/tui/src/terminal_hyperlinks.rs near line 392, where text[source_byte..wrapped.range.start] panics. Trace where wrapped.range values come from, since the invalid offset is the upstream cause, and note that the #52330 clamp does not cover it. Done means a regression test that remaps long CJK text with emoji such as ➡️ across several wrap widths without panicking, with visible text and source mappings preserved.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

bug CLI TUI
What version of Codex CLI is running?

codex-cli 0.162.0, installed globally via npm (@openai/codex). The npm latest endpoint also returned 0.162.0 when checked.

What subscription do you have?

Not provided.

Which model were you using?

Not confirmed for the crashing turn.

What platform is your computer?

Linux 7.0.0-38-generic x86_64 GNU/Linux.

What terminal emulator and version are you using (if applicable)?

Kitty 0.49.0, with zsh.

Codex doctor report

Not collected. No account credentials or private workspace logs are included in this report.

What issue are you seeing?

The interactive Codex CLI panicked and exited to the shell while handling a Chinese question containing emoji. The terminal retained this error:

The application panicked (crashed).
Message: end byte index 159 is not a char boundary; it is inside '➡' (bytes 158..161) of [application text omitted for privacy]
Location: tui/src/terminal_hyperlinks.rs:392

Backtrace omitted. Run with RUST_BACKTRACE=1 environment variable to display it.
Run with RUST_BACKTRACE=full to include source snippets.
What steps can reproduce the bug?

This is an observed crash, not yet a deterministic end-to-end reproducer. The exact terminal dimensions and triggering UI action were not captured, and a full backtrace is unavailable.

  1. Run codex version 0.162.0 in Kitty.
  2. The affected interaction contains a long Chinese question, including ➡️ (business text omitted).
  3. The TUI exits with the panic above during source-range remapping.

The application's business text has been omitted for privacy. The original panic identifies ➡ at UTF-8 bytes 158..161; offset 159 is inside that character.

What is the expected behavior?

Rendering/wrapping Chinese text and emoji should not terminate the CLI. Source ranges used for slicing should remain valid UTF-8 boundaries and correctly map to the displayed text.

Additional information

The reported location matches the code in the 0.162.0 tag:
https://github.com/openai/codex/blob/rust-v0.162.0/codex-rs/tui/src/terminal_hyperlinks.rs#L392

Inside remap_source_wrapped_line:

source_column += display_width(&text[source_byte..wrapped.range.start]);

The panic indicates that the range start used here was inside a multibyte character. The upstream cause of the invalid wrapped range still needs investigation; this report does not establish that the arrow alone always triggers a crash.

Related change: #52330 (commit 22ebb0fb178fe369190123c256ba200585765725) clamps wrapped range offsets to text.len() to address a cursor sentinel past the end of the input. That particular clamp does not address this case: 159 is already below the input length but is not a character boundary. A local Python byte-boundary check using the reported text confirmed that min(159, len(text.encode("utf-8"))) remains 159 and the prefix still fails UTF-8 decoding. This was a boundary check only, not a Rust/TUI regression test.

Suggested investigation/regression coverage: exercise source-range remapping of long CJK questions with emoji/variation selectors across different wrap widths, and check both in-bounds character boundaries and preservation of visible text/source mappings.

Lingua principale
Rust
Stelle
133k
Fork
21.1k
Merge medio
1m
PR unite (30g)
997

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di openai/codex

Tutte le issue di openai/codex

Issue simili

Altre issue su Rust

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.