nh icon indicating copy to clipboard operation
nh copied to clipboard

Download progress not showing

Open biscotty666 opened this issue 1 month ago • 7 comments

I have confirmed that this is a bug related to nh

  • [x] This is a bug, and not an user error or a support request. I understand that my issue will be closed if it is not a bug in NH.
  • [x] I have checked the issues tab and confirmed that my issue has not yet been reported. I understand that my issue will be closed if it is a duplicate.

Description

When doing a build or switch, the progress area does not show any progress for downloading packages. It shows the number of packages to be downloaded as paused, even as they are downloading, and remains so even when the downloading is finished. The build section works as usual, showing progress as packages are built. I don't really remember when I first noticed, but it's at least a week now I think. Thank you.

Installation Method

Stable Release (nixpkgs, pkgs.nh from nixos-unstable or nixos-yy-mm)

Installation Method (Other)

No response

NH Version

4.2.0

System Information

  • system: "x86_64-linux"
  • host os: Linux 6.12.53, NixOS, 25.11 (Xantusia), 25.11.20251019.5e2a59a
  • multi-user?: yes
  • sandbox: yes
  • version: nix-env (Nix) 2.31.2
  • channels(root): "nixos-23.11"
  • nixpkgs: /nix/store/7agp54mgffm9m1wc1kgmkm37pvy18qhf-source

biscotty666 avatar Oct 21 '25 13:10 biscotty666

This is a nom bug https://github.com/maralorn/nix-output-monitor/issues/201

bestlem avatar Oct 21 '25 13:10 bestlem

This is a nom bug maralorn/nix-output-monitor#201

seems they are already fixed it https://github.com/maralorn/nix-output-monitor/commit/20758af18c6b5969ba5493bb3883031209e4364d

any ideas how to fix it in nh?

tempergate avatar Oct 27 '25 05:10 tempergate

Overlay nix-output-monitor to build it from master branch until a new release hits nixpkgs. There is nothing we can do on nh's end besides rewriting nom as a rust crate and getting rid of it entirely.

NotAShelf avatar Oct 27 '25 06:10 NotAShelf

Overlay nix-output-monitor to build it from master branch until a new release hits nixpkgs. There is nothing we can do on nh's end besides rewriting nom as a rust crate and getting rid of it entirely.

i've tried to install it from nix-output-monitor, and add a variable like NH_NOM = "${nom.packages.${pkgs.system}.default}/bin/nom"; , am I correct?

tempergate avatar Oct 27 '25 09:10 tempergate

No, NH_NOM takes a boolish value and not a path.

I could make it take a path instead (and use a different variable for controlling nom) but since nix-output-monitor is available in nixpkgs nh's closure, that is the least efficient way to do it imo. You should instead use the overlay as described above to avoid bad surprises.

NotAShelf avatar Oct 27 '25 10:10 NotAShelf

No, NH_NOM takes a boolish value and not a path.

I could make it take a path instead (and use a different variable for controlling nom) but since nix-output-monitor is available in nixpkgs nh's closure, that is the least efficient way to do it imo. You should instead use the overlay as described above to avoid bad surprises.

i've tried to install it from nom flake adding ' environment.systemPackages = [ nom.packages.${pkgs.system}.default ]; '

seems it nothing changes

tempergate avatar Oct 27 '25 10:10 tempergate

Once again, you need to use an overlay. nh pulls nix-output-monitor in the package expression. You need to override it, not pull nix-output-monitor in systemPackages.

NotAShelf avatar Oct 27 '25 10:10 NotAShelf