!lymvtcwDJ7ZA9Npq:lix.systems

Lix Development

419 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
17 May 2024
@qyriad:katesiria.orgQyriad
In reply to@jade_:matrix.org
rust ppl even have a nice gh review process as far as gh review processes go, they have bors so they can merge-queue things, have good reviewer assignment, bors d+ to delegate merging to the author after they fix something minor, and more
(And look how much work they had to reinvent to make Github review even bearable)
01:10:16
@jade_:matrix.orgjade_that's correct01:10:21
@qyriad:katesiria.orgQyriadOh yeah Gerrit needs to be refreshed to update basically anything correctly. It sucks01:10:30
@jade_:matrix.orgjade_i think it's to workaround the big gerrit instances being slow01:10:44
@jade_:matrix.orgjade_ours is fast as fuck though because it is not big01:10:50
@julia:the-apothecary.clubjuliaI have pressed the merge button 🎉01:11:02
@qyriad:katesiria.orgQyriadCongratulations~01:11:24
@qyriad:katesiria.orgQyriadbtw feel free to add anything you think might be handy to https://wiki.lix.systems/books/lix-contributors/page/gerrit01:13:11
@qyriad:katesiria.orgQyriadyou should have edit perms01:13:14
@jade_:matrix.orgjade_image.png
Download image.png
01:13:56
@jade_:matrix.orgjade_scuffed patch!!01:13:57
@jade_:matrix.orgjade_go brr!!!01:14:00
@qyriad:katesiria.orgQyriadoh niiiice01:14:22
@julia:the-apothecary.clubjulia?01:14:23
@qyriad:katesiria.orgQyriad"Code Review (Gerrit)" link01:14:33
@julia:the-apothecary.clubjuliaoh the tab01:14:34
@julia:the-apothecary.clubjuliaI thought was referring to the 1088 change fsr01:15:00
@raitobezarius:matrix.orgraitobezarius
In reply to @jade_:matrix.org
sent an image.
beautiful
01:16:32
@jade_:matrix.orgjade_image.png
Download image.png
01:28:35
@jade_:matrix.orgjade_shipped on actual lix now01:28:35
@qyriad:katesiria.orgQyriad thank you jade! 01:29:34
@raitobezarius:matrix.orgraitobezariusthe coolitude is infinite01:35:30
@raitobezarius:matrix.orgraitobezariusi almost want it for my own forgejo now01:35:39
@julia:the-apothecary.clubjuliahttps://buildbot.lix.systems/#/buildrequests/74273 hm how do I debug tests in CI failing when I can't access the test log02:24:50
@julia:the-apothecary.clubjulia * https://buildbot.lix.systems/#/buildrequests/74273 hm how do I debug tests in CI failing when I can't access the test log (from https://gerrit.lix.systems/c/lix/+/1127)02:26:48
@julia:the-apothecary.clubjulia * https://buildbot.lix.systems/#/buildrequests/74273 hm how do I debug tests in CI failing when I can't access the test log (from https://gerrit.lix.systems/c/lix/+/1127); also re: the nixos/github-flakes.nix test - it servers the registry by faking channels.nixos.org, but since I've deprecated online flake registry.... that won't work. should I (a) set the flake-registry to point to channels.nixos.org to test the remote fetch feature (even though its deprecated), or (b) set it to the file directory?02:28:32
@jade_:matrix.orgjade_
In reply to @julia:the-apothecary.club
https://buildbot.lix.systems/#/buildrequests/74273 hm how do I debug tests in CI failing when I can't access the test log (from https://gerrit.lix.systems/c/lix/+/1127);

also re: the nixos/github-flakes.nix test - it servers the registry by faking channels.nixos.org, but since I've deprecated online flake registry.... that won't work. should I (a) set the flake-registry to point to channels.nixos.org to test the remote fetch feature (even though its deprecated), or (b) set it to the file directory?
you are supposed to have access to the log
02:34:52
@julia:the-apothecary.clubjuliaI have the stdout log02:35:05
@julia:the-apothecary.clubjuliabut the meson tests logs is in the build dir?02:35:11
@julia:the-apothecary.clubjulia * but the meson tests logs is in the build dir which I can't see?02:35:24

Show newer messages


Back to Room ListRoom Version: 10