Broken pipe error upon nix log #798

Open
opened 2025-04-13 04:07:56 +00:00 by winter · 2 comments
Member

Describe the bug

Upon quitting the pager that nix log spawns, I consistently get error: writing to file: Broken pipe.

Steps To Reproduce

  1. nix log /nix/store/some.drv
  2. Quit pager (e.g. q in less)
  3. See error

Expected behavior

It shouldn't error, the pager's gone.

nix --version output

nix (Lix, like Nix) 2.92.0-pre20250118-0795280
System type: aarch64-darwin
Additional system types: x86_64-darwin
Features: gc, signed-caches
System configuration file: /etc/nix/nix.conf
User configuration files: /Users/winter/.config/nix/nix.conf:/Users/winter/.nix-profile/etc/xdg/nix/nix.conf:/run/current-system/sw/etc/xdg/nix/nix.conf:/nix/var/nix/profiles/default/etc/xdg/nix/nix.conf
Store directory: /nix/store
State directory: /nix/var/nix
Data directory: /nix/store/18bgwnnqsrdnsqqab889y1gwhg4f31rf-lix-2.92.0-pre20250118-0795280/share

Additional context

This only very recently (within the last few hours) started happening, and I'm not sure why; I didn't touch anything on my system (e.g. less version, Lix version, etc.).

## Describe the bug Upon quitting the pager that `nix log` spawns, I consistently get `error: writing to file: Broken pipe`. ## Steps To Reproduce 1. `nix log /nix/store/some.drv` 2. Quit pager (e.g. `q` in `less`) 3. See error ## Expected behavior It shouldn't error, the pager's gone. ## `nix --version` output ``` nix (Lix, like Nix) 2.92.0-pre20250118-0795280 System type: aarch64-darwin Additional system types: x86_64-darwin Features: gc, signed-caches System configuration file: /etc/nix/nix.conf User configuration files: /Users/winter/.config/nix/nix.conf:/Users/winter/.nix-profile/etc/xdg/nix/nix.conf:/run/current-system/sw/etc/xdg/nix/nix.conf:/nix/var/nix/profiles/default/etc/xdg/nix/nix.conf Store directory: /nix/store State directory: /nix/var/nix Data directory: /nix/store/18bgwnnqsrdnsqqab889y1gwhg4f31rf-lix-2.92.0-pre20250118-0795280/share ``` ## Additional context This only very recently (within the last few hours) started happening, and I'm not sure why; I didn't touch anything on my system (e.g. `less` version, Lix version, etc.).
Owner

reproducible with any build log and PAGER=false, or anything else that exits before lix has fed the entire log to the pager

reproducible with any build log and `PAGER=false`, or anything else that exits before lix has fed the entire log to the pager
Owner

upon inspection this turns out to be very involved to fix because once again nix is a steaming pile of garbage and uses no less than three different methods of producing output that is fed to the pager, none of which can actually deal with being told to stop.

upon inspection this turns out to be very involved to fix because once again nix is a steaming pile of garbage and uses no less than three different methods of producing output that is fed to the pager, none of which can actually deal with being told to stop.
Sign in to join this conversation.
No milestone
No project
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: lix-project/lix#798
No description provided.