!lymvtcwDJ7ZA9Npq:lix.systems

Lix Development

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

Load older messages


SenderMessageTime
18 Mar 2026
@raitobezarius:matrix.orgraitobezariusGerrit understands the kinds of delta a patchset23:14:19
@raitobezarius:matrix.orgraitobezariusA NO_CODE_CHANGE won't trigger CI23:14:35
@raitobezarius:matrix.orgraitobezariusChanging a character will trigger CI, yes23:14:47
@piegames:flausch.socialpiegames
In reply to @piegames:flausch.social
You can get permissions if you ask, though I forgot where to ask 🙃
I restate my position here that retriggering CI builds should not be a gated permission and instead be accessible to all logged-in users
23:17:53
@blokyk:matrix.orgzoë (she/her)if you can't remember i can just change the release notes slightly, that should be enough x)23:18:19
@blokyk:matrix.orgzoë (she/her)* if you can't remember i can just change the release notes slightly, that should be enough x) edit: aaand it's pushed & restarted, thx folks23:20:15
@raitobezarius:matrix.orgraitobezarius
In reply to @piegames:flausch.social
I restate my position here that retriggering CI builds should not be a gated permission and instead be accessible to all logged-in users
I did not buy the Buildkite company yet alas
23:20:31
@raitobezarius:matrix.orgraitobezarius(and I am not sure that a bot would make things more discoverable but maybe, not sure)23:21:50
@delroth:delroth.netdelrothCI failure UI on the gerrit side could include instructions on how to retrigger via bot23:22:39
@delroth:delroth.netdelroth(and I presume besadii could listen for gerrit CL comments, for example?)23:23:03
@raitobezarius:matrix.orgraitobezariusYup23:24:24
19 Mar 2026
@sky1e:mildlyfunctional.gaysky1eWhen I encounter a spurious CI failure, what I do is wait until someone else merges a cl and rebase my change on top and push. Not always the fastest, but doesn't involve asking anyone for help, which I'm rather bad at 🙃02:00:05
@winter:catgirl.cloudWinter

raitobezarius doing a bit of maintenance to the lix package set in nixpkgs, i remember mention of some weird self ref in nix-direnv. when trying to repro that, it appears that… all packages in the set are currently infreccing? e.g.:

(import ./. {
  overlays = [(f: p: { inherit (p.lixPackageSets.latest) nixpkgs-review; })];
}).nixpkgs-review
03:29:31
@winter:catgirl.cloudWinteris this known?03:29:35
@aloisw:kde.orgaloiswYes, it is known that overlaying like this does not work. The only things it works for are Lix itself and its nix-eval-jobs.05:24:19
@winter:catgirl.cloudWinteri was under the (i guess false!) impression that it was only for a handful of bad derivations (e.g. nix-direnv), but i guess it’s actually never worked at all? it should probably be removed from the website then if this is indeed true05:35:14
@winter:catgirl.cloudWinter there was a Lix discussion at the time, but https://git.lix.systems/lix-project/lix-website/commit/26676b416a334fb69a7f6a2ac3d8464f321f4cca is what i remember 05:37:38
@raitobezarius:matrix.orgraitobezarius https://git.lix.systems/lix-project/lix/issues/980#issue-14093 it's known for the past 6 months 09:08:57
@raitobezarius:matrix.orgraitobezariuswith no resolution yet09:08:59
@raitobezarius:matrix.orgraitobezariuswe are planning to delete these instructions09:09:04
@lisanna-dettwyler:matrix.orgLisannais there a process for cloning a cppnix issue into the lix issue tracker? or does it happen automatically20:17:19
@raitobezarius:matrix.orgraitobezariusthere's no automation of the sort as we have diverged quite20:24:39
@raitobezarius:matrix.orgraitobezariusso we usually want people to open their own issues they encountered on lix20:24:53
@raitobezarius:matrix.orgraitobezarius(mentions of cppnix sharing the same issue are welcome but are not super useful these days imho except if it's certain by the reporter there's a shared subsystem there)20:25:10
@sky1e:mildlyfunctional.gaysky1e

I noticed when hacking on lix's JSON parser that it silently accepts duplicate json object keys, throwing away all but the last one. Is this known and desired behavior? I tried making it crash instead and it seemed to still pass all of the tests, so this behavior isn't being tested for.
nix eval --expr 'builtins.fromJSON '"''"'{"a":"a","a":"b"}'"''"

{ a = "b"; }

23:17:47
* @piegames:flausch.socialpiegames sighs23:38:57
@piegames:flausch.socialpiegamesThis language truly is a gift23:39:07
@sky1e:mildlyfunctional.gaysky1eShall I file an issue then?23:39:42
@xokdvium:matrix.orgSergei Zimmerman (xokdvium)
In reply to @piegames:flausch.social
This language truly is a gift
I wouldn’t be surprised if that changed from 2.3 when nlohmann was introduced
23:47:32
@piegames:flausch.socialpiegames
In reply to @sky1e:mildlyfunctional.gay
Shall I file an issue then?
Yes please
23:47:55

Show newer messages


Back to Room ListRoom Version: 10