!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.138 Servers

Load older messages


SenderMessageTime
16 May 2024
@samrose:matrix.orgsamrose
In reply to @qyriad:katesiria.org
Python's fine, and it's already part of the buildsystem in other ways. If there's something that's a better idea or more preferred for another reason we can talk about that too
It would be nice if someone had written a general cli testing suit in Rust, or Go (which likely would make the test suite run faster) but I am not aware of anything that exists. I think the Rust cli tool community gravitated toward using python due to Pexpect, and a lot of existing tools that are good fit for test suite.
17:37:19
@samrose:matrix.orgsamrose(it seems like functional tests need the most help basically if I am not mistaken. Apologies if you basically already said this)17:38:19
@qyriad:katesiria.orgQyriadno they definitely do. those are the "bash" flavor of tests17:38:40
@samrose:matrix.orgsamrosehttps://git.lix.systems/lix-project/lix/src/branch/main/tests/functional17:38:51
@qyriad:katesiria.orgQyriadyep17:38:57
@qyriad:katesiria.orgQyriadsomething that probably could be migrated separately is the stuff that sets up the daemon the test suite uses17:39:16
@aprl:uwu.isaprl (GPN; DECT 2774; SIP GAYS) joined the room.18:30:38
@puck:puck.moepuck domen?? https://github.com/NixOS/nixpkgs/blob/741342772c768588878be460f0e1aa9e6d8d0caa/pkgs/by-name/de/devenv/package.nix#L19-L30 18:45:40
@qyriad:katesiria.orgQyriado.o18:46:06
@puck:puck.moepuckpushed a fix lmao18:51:40
@qyriad:katesiria.orgQyriad Wait to what 18:52:17
@puck:puck.moepuck nixos-module; devenv wouldn't build with the overlay attached because it overrided the source of pkgs.nix 18:52:41
@puck:puck.moepuck * nixos-module; devenv wouldn't build with the overlay attached because it locally overrided the source of pkgs.nix 18:52:47
@puck:puck.moepuckand the build system changes meant that it broke18:52:54
@puck:puck.moepuck https://git.lix.systems/lix-project/nixos-module/commit/53d713eb486f21d653af3ef3528e9a19ecfc45e5 18:54:09
@qyriad:katesiria.orgQyriadahh19:01:23
@qyriad:katesiria.orgQyriadty19:01:25
@raitobezarius:matrix.orgraitobezarius (DECT: 7248)
In reply to @puck:puck.moe
domen?? https://github.com/NixOS/nixpkgs/blob/741342772c768588878be460f0e1aa9e6d8d0caa/pkgs/by-name/de/devenv/package.nix#L19-L30
oh so we found another fork of nix?
19:10:20
@delroth:delroth.netdelroth
In reply to @raitobezarius:matrix.org
oh so we found another fork of nix?
Literally, you can't make this up.
19:14:05
@raitobezarius:matrix.orgraitobezarius (DECT: 7248)Redacted or Malformed Event19:14:19
@morguwuldir:uwu.sulian.eumorguwuldir 🏳️‍⚧️ set a profile picture.22:46:38
@delroth:delroth.netdelroth Qyriad: if you have some time I'd love some input on whether the fix I have in mind for https://git.lix.systems/lix-project/lix/issues/312 is what you also had in mind (if you did have a fix in mind) / something that matches your expectations 22:49:57
@delroth:delroth.netdelroth(also if you'd rather have no ping here for stuff like that because you process bug / CL notifications async, lmk, I have no clue how y'all work so I'm defaulting to over-notifying...)22:50:28
@qyriad:katesiria.orgQyriadFailing at parse time is the solution we envisioned22:53:59
@qyriad:katesiria.orgQyriadWe had the E/easy on there since we imagined it would be as simply as changing the assertion to a user-facing error message, but seem to have underestimated the difficulty in that itself, oops22:54:40
@qyriad:katesiria.orgQyriad(And yeah pinging us like this is fine)22:55:42
@jade_:matrix.orgjade_ Qyriad: ok if we stage the libnixexpr->liblixexpr etc change? 22:57:23
@jade_:matrix.orgjade_(pinging as assignee)22:57:42
@delroth:delroth.netdelroth
In reply to @qyriad:katesiria.org
We had the E/easy on there since we imagined it would be as simply as changing the assertion to a user-facing error message, but seem to have underestimated the difficulty in that itself, oops
nah I think that if you had explained your envisioned fix it would have been fairly trivial but having to independently come to the same conclusion without having the same background was harder :P
22:57:50
@delroth:delroth.netdelroth still, happy it was the same conclusion (roughly - I think rejecting at parsing time is better than failing when making the worker goals, but that's tiny details) 22:58:22

Show newer messages


Back to Room ListRoom Version: 10