!lymvtcwDJ7ZA9Npq:lix.systems

Lix Development

408 Members
(Technical) development of Lix, the package manager, a Nix implementation. Please be mindful of ongoing technical conversations in this channel.136 Servers

Load older messages


SenderMessageTime
12 Nov 2025
@winter:catgirl.cloudWinter do we want to simply remove that note from the readme, or change nrWorkers to actually default to nproc? 20:12:19
@ma27:nicht-so.sexyma27my personal preference would be to keep the behavior as-is and just fix the docs.20:15:45
@winter:catgirl.cloudWintergotcha20:45:11
@winter:catgirl.cloudWinterlearning that n-e-j doesn20:45:15
@winter:catgirl.cloudWinter...'t die on sigpipe and groaning20:45:23
@raitobezarius:matrix.orgraitobezarius i think there's a bunch of CL improvements from aloisw on n-e-j 21:56:52
13 Nov 2025
@aloisw:julia0815.dealoisw SIGPIPE is not in it though. Also it seems like the entirety of Lix just ignores it completely. I think the best way forward would not be to special-case it in nix-eval-jobs, but to treat as an interrupt like SIGTERM and SIGHUP. 05:59:10
@winter:catgirl.cloudWinteri believe i only looked at nix but it appears that they’re not explicitly ignoring it at least, instead just saying to use the OS’ default signal handler for it?06:15:06
@winter:catgirl.cloudWinterand yeah, agreed06:15:10
@winter:catgirl.cloudWinterguess i could write a patch for that pretty easily06:15:40
@winter:catgirl.cloudWinteronce i wrap my head around the current state of affairs described above06:15:49
@aloisw:julia0815.dealoisw
In reply to @winter:catgirl.cloud
i believe i only looked at nix but it appears that they’re not explicitly ignoring it at least, instead just saying to use the OS’ default signal handler for it?
https://git.lix.systems/lix-project/lix/src/commit/78bdc60c11031d2293b2e77a0e44140ff7b88f12/lix/libutil/signals.cc#L189-L197
07:25:58
@aloisw:julia0815.dealoisw The solution I imagined above was just adding SIGPIPE here: https://git.lix.systems/lix-project/lix/src/commit/78bdc60c11031d2293b2e77a0e44140ff7b88f12/lix/libutil/signals.cc#L119 07:26:54
@aloisw:julia0815.dealoisw Of course that's not going to work because SIGPIPE is only sent to the writing thread. 11:45:10
@alicia:catgirl.cloudAlicia joined the room.22:44:56
15 Nov 2025
@347online:matrix.orgKatie joined the room.18:22:52
16 Nov 2025
@grimmauld:grapevine.grimmauld.deGrimmauld (any/all) Quick heads-up:
I believe https://git.lix.systems/lix-project/lix/src/commit/e101400359558ec89f0a3afa29631ca1b6546fd3/lix/libutil/processes.cc#L20-L22 should be unconditional. On glibc gcc this header is included implicitly. On musl llvm, that include is needed or otherwise SYS_capset (https://git.lix.systems/lix-project/lix/src/commit/243836ed0a0b963eebd033d109e6cb817d67fde4/lix/libutil/processes.cc#L414) is undefined.
08:49:40
@xokdvium:matrix.orgSergei Zimmerman (xokdvium)

On my dev machine I'm getting:

+(tarball.sh:31) nix-build -o /tmp/nix-test/tarball/result -E 'import (fetchTarball { url = "file:///does-not-exist/must-remain-unused//tmp/nix-test/tarball/tarball.tar"; sha256 = "sha256-PRgXPIzueCAIFHesj5pSLlDYbJsrGmUD8B9gpbs9p9Q="; })'
++(tarball.sh:36) mktemp -d
+(tarball.sh:36) export HOME=/tmp/tmp.0S4oIlI3Xo
+(tarball.sh:36) HOME=/tmp/tmp.0S4oIlI3Xo
tarball.sh: line 37: TMPDIR: unbound variable

Seems like function tests need to provide a sensible default for TMPDIR if it's not set

23:49:08
@xokdvium:matrix.orgSergei Zimmerman (xokdvium) *

On my dev machine I'm getting:

+(tarball.sh:31) nix-build -o /tmp/nix-test/tarball/result -E 'import (fetchTarball { url = "file:///does-not-exist/must-remain-unused//tmp/nix-test/tarball/tarball.tar"; sha256 = "sha256-PRgXPIzueCAIFHesj5pSLlDYbJsrGmUD8B9gpbs9p9Q="; })'
++(tarball.sh:36) mktemp -d
+(tarball.sh:36) export HOME=/tmp/tmp.0S4oIlI3Xo
+(tarball.sh:36) HOME=/tmp/tmp.0S4oIlI3Xo
tarball.sh: line 37: TMPDIR: unbound variable

Seems like functional tests need to provide a sensible default for TMPDIR if it's not set

23:49:27
17 Nov 2025
@raitobezarius:matrix.orgraitobezariusCan you open an issue with this trace so I don't forget about it? Thanks!00:03:55
@xokdvium:matrix.orgSergei Zimmerman (xokdvium)https://git.lix.systems/lix-project/lix/issues/103500:09:21
@olivia:computer.surgeryolivia changed their profile picture.00:23:19
@xokdvium:matrix.orgSergei Zimmerman (xokdvium)Also any clue as to what's going on here? https://buildkite.com/lix-project/lix/builds/5888/steps/canvas?sid=019a8f19-65cf-4acd-9593-5d6bcd790abf#019a8f19-668b-4cbb-99c2-e68a72269606/18-32 The error message is coming from the host lix and not the one that's being built? Seems fucked00:25:14
@raitobezarius:matrix.orgraitobezariusI am going to take a look, I hope I didn't fuck up something with my recent infra work00:28:24
@raitobezarius:matrix.orgraitobezariusNormally I didn't touch this host neither its daemon setup00:28:35
@shalokshalom:kde.orgShalokShalom joined the room.07:52:34
@shalokshalom:kde.orgShalokShalomThe email confirmation for your git doesn't let me in, so I drop this here: https://nix-community.github.io/home-manager/index.xhtml#sec-usage-gpu-non-nixos This new mode for GPU support got merged last week. You might wanna update the README, that speaks about NixGL (only)07:53:37
@522_:catgirl.cloud522 it/its ⛯ΘΔ wrong room? may be looking for #home-manager:nixos.org 11:22:49
@522_:catgirl.cloud522 it/its ⛯ΘΔor11:23:19
@522_:catgirl.cloud522 it/its ⛯ΘΔdoes lix's readme have a mention of nixgl?11:23:33

Show newer messages


Back to Room ListRoom Version: 10