astral-sh/uv

uv panics when resizing terminal window

Open

#12,244 opened on Mar 17, 2025

View on GitHub
 (6 comments) (2 reactions) (0 assignees)Rust (84,934 stars) (3,111 forks)batch import
bughelp wanted

Description

Summary

Whenever i resize my terminal window, I get spammed with the following (or similar) errors for as long as I am resizing my window. I started getting these when a switch to using ghostty as my terminal app and am wondering if the refresh/repaint interval on the resize is just faster than expected.

❯ thread 'main2' panicked at /Users/brew/Library/Caches/Homebrew/cargo_cache/registry/src/index.crates.io-6f17d22bba15001f/clap_complete-4.5.44/src/aot/shells/fish.rs:45:33:
failed to write completion file: Os { code: 32, kind: BrokenPipe, message: "Broken pipe" }
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
thread 'main' panicked at /private/tmp/uv-20250219-7867-jnorhr/uv-0.6.2/crates/uv/src/lib.rs:1933:10:

When i enable the full backtrace im getting:

❯ thread 'main2' panicked at /Users/brew/Library/Caches/Homebrew/cargo_cache/registry/src/index.crates.io-6f17d22bba15001f/clap_complete-4.5.44/src/aot/shells/fish.rs:269:8:
failed to write completion file: Os { code: 32, kind: BrokenPipe, message: "Broken pipe" }
stack backtrace:
   0:        0x1004b8e70 - __mh_execute_header
   1:        0x1001a04cc - __mh_execute_header
   2:        0x1004b8c64 - __mh_execute_header
   3:        0x1004b7638 - __mh_execute_header
   4:        0x1004b9334 - __mh_execute_header
   5:        0x1004b92a4 - __mh_execute_header
   6:        0x1004b6da4 - __mh_execute_header
   7:        0x101643640 - __mh_execute_header
   8:        0x1016435cc - __mh_execute_header
   9:        0x1001915c4 - __mh_execute_header
  10:        0x10069c338 - __mh_execute_header
  11:        0x100685184 - __mh_execute_header
  12:        0x100c802ec - __mh_execute_header
  13:        0x10009a5ec - __mh_execute_header
  14:        0x100495810 - __mh_execute_header
  15:        0x18101c2e4 - __pthread_deallocate
thread 'main' panicked at /private/tmp/uv-20250219-7867-jnorhr/uv-0.6.2/crates/uv/src/lib.rs:1933:10:
Tokio executor failed, was there a panic?: Any { .. }
stack backtrace:
   0:        0x1004b8e70 - __mh_execute_header
   1:        0x1001a04cc - __mh_execute_header
   2:        0x1004b8c64 - __mh_execute_header
   3:        0x1004b7638 - __mh_execute_header
   4:        0x1004b9334 - __mh_execute_header
   5:        0x1004b92a4 - __mh_execute_header
   6:        0x1004b6da4 - __mh_execute_header
   7:        0x101643640 - __mh_execute_header
   8:        0x1016435cc - __mh_execute_header
   9:        0x100da1eec - __mh_execute_header
  10:        0x100c7c7fc - __mh_execute_header

system details:

❯ neofetch
                    'c.          steve@Aviendha.local
                 ,xNMM.          --------------------
               .OMMMMo           OS: macOS 15.3.2 24D81 arm64
               OMMM0,            Host: MacBookPro18,2
     .;loddo:' loolloddol;.      Kernel: 24.3.0
   cKMMMMMMMMMMNWMMMMMMMMMM0:    Uptime: 2 hours, 34 mins
 .KMMMMMMMMMMMMMMMMMMMMMMMWd.    Packages: 424 (brew)
 XMMMMMMMMMMMMMMMMMMMMMMMX.      Shell: fish 3.7.1
;MMMMMMMMMMMMMMMMMMMMMMMM:       Resolution: 5120x1440
:MMMMMMMMMMMMMMMMMMMMMMMM:       DE: Aqua
.MMMMMMMMMMMMMMMMMMMMMMMMX.      WM: Quartz Compositor
 kMMMMMMMMMMMMMMMMMMMMMMMMWd.    WM Theme: Blue (Light)
 .XMMMMMMMMMMMMMMMMMMMMMMMMMMk   Terminal: ghostty
  .XMMMMMMMMMMMMMMMMMMMMMMMMK.   CPU: Apple M1 Max
    kMMMMMMMMMMMMMMMMMMMMMMd     GPU: Apple M1 Max
     ;KMMMMMMMWXXWMMMMMMMk.      Memory: 8484MiB / 65536MiB
       .cooc,.    .,coo:.

Platform

macOS 15.3

Version

uv 0.6.2

Python version

Python 3.12.9

Contributor guide

Tech stack
rustshell
Domain
cli
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Rust programmingunderstanding of terminal signalsfamiliarity with clap complete
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40
Research direction
Investigate the panic in clap complete's fish.rs at line 45 and 269 when writing completion files. The panic occurs due to a BrokenPipe error, likely caused by terminal resize signals (SIGWINCH). Consider adding error handling to gracefully handle BrokenPipe errors during completion file writing, or investigate if uv's tokio executor can catch this. Also check /private/tmp/uv 0.6.2/crates/uv/src/lib.rs:1933 for the panic in the tokio executor.