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

Load older messages


SenderMessageTime
1 Jun 2024
@jade_:matrix.orgjade_
In reply to @raitobezarius:matrix.org
jade_: is there anything i can do to help you on the release engineering scripts you are working on? or take some load off you?
i am currently busy with guests here, but hm. i think one thing that would be good is if the installer build stuff were somehow nicely integrated into the overall releng scripts. but idk, hard to really point at easily separable tasks.
18:33:54
@draupnir:lix.systemsdraupnirchanged room power levels.18:38:10
@jade_:matrix.orgjade_ I would also like to not need an arm mac to build the installer 18:39:38
@jade_:matrix.orgjade_at least for testing18:39:48
@raitobezarius:matrix.orgraitobezarius set the room topic to "(Technical) development of Lix, the package manager, a Nix implementation. Please be mindful of ongoing technical conversations in this channel.".18:51:27
@qyriad:katesiria.orgQyriad
In reply to@kloenk:kloenk.eu
only getting a You do not have the can-perform-mutations buildbot role. I just want to see some log what actually failed
Currently only existing contributors can see the buildbot logs — just becauase buildbot as it is doesn't have any way to allow only certain people to do things like forcibly cancel or restart arbitrary builds, which is something we intend to fix
21:19:19
@kloenk:kloenk.eukloenkah fair. can you tell me what it says? localy the check (only on x86 linux, everything else does not have a test) does succeed. so unsure what to do, or if it's just flakey21:21:54
@qyriad:katesiria.orgQyriadugh, a remote builder failure. restarted the build21:23:52
@qyriad:katesiria.orgQyriaddidn't realize that was your CL; we'll fix your permissions21:24:21
@pennae:matrix.eno.space⚠️ eldritch horrors operating in this area ⚠️the remote builder should get fixed again, sorry <,<21:25:29
@qyriad:katesiria.orgQyriadthere you go; you might have to log out and log back in, but you should have buildbot perms and issue triage perms in forgejo21:25:31
@tim:stratum0.orgdadada joined the room.21:26:25
@kloenk:kloenk.eukloenkah thanks works. good to hear that it's nothing with my change :)21:48:59
@qyriad:katesiria.orgQyriadas heads up, your change will probably be deferred until after we finish 2.9021:49:36
@kloenk:kloenk.eukloenkNo worries. I waited 4 years in nixcpp :p22:06:15
@charles:computer.surgeryCharles joined the room.22:31:41
@ma27:nicht-so.sexyma27

Question: is there any way in a DerivationGoal to find out whether you're in a daemon or in a nix-build as a root? I'm a little out of ideas since the store is always a LocalStore here and I didn't manage to write dynamic_cast<SimpleLogger> since that's not implemented in any of the headers.

Context: a while ago I submitted https://gerrit.lix.systems/c/lix/+/913 to get SSH errors in the stderr of a nix-build and I think I found a nicer solution than this (using logger->log basically in DerivationGoal::tryBuildHook).
THe idea is to still use writeStderr (to have errors actually appear in nix-daemon stderr) and to use logger to make it appear in the client's stderr. Then we can probably get rid of the log-fd=4 thingy, at least for ssh-ng (for legacy ssh tests are breaking badly and I'm not entirely sure why yet).

Any ideas? Or is my idea even reasonable?

22:46:03
@ma27:nicht-so.sexyma27 oh I should probably explain why I want to know: if I do sudo nix-build, I don't go via the daemon and logger->log & writeStderr would write into the "same" stderr, i.e. SSH messages would always appear twice. 22:47:05
@pennae:matrix.eno.space⚠️ eldritch horrors operating in this area ⚠️it'd probably be better to always go through nix-daemon if one exists and treat nix-build without faemin as disaster recovery that needn't be super prettt22:52:07
@artemist:mildlyfunctional.gayartemist joined the room.22:55:20
@ma27:nicht-so.sexyma27

yeah I only realized that because lazy me was doing sudo ./result/bin/nix to avoid changing my system's daemon %)

but, do you want me to submit a change going into that direction?
and regarding the change I'm currently working on, your suggestion is basically to just accept duplicated messages when "bypassing" the daemon on a remote build?

22:57:51
@ma27:nicht-so.sexyma27or did I misunderstand that? :)22:57:56
@pennae:matrix.eno.space⚠️ eldritch horrors operating in this area ⚠️no you got it right22:58:23
@artemist:mildlyfunctional.gayartemistIs there a plan to setup gerrit for lix-installer? I'm working on fixing the tests so I can do more development22:58:36
@ma27:nicht-so.sexyma27

ok, thanks for your input!

will try to submit a a CL for that soonish.

but I think I'll go to sleep first :)

22:59:35
@qyriad:katesiria.orgQyriad
In reply to @pennae:matrix.eno.space
it'd probably be better to always go through nix-daemon if one exists and treat nix-build without faemin as disaster recovery that needn't be super prettt
yes, agreed. root defaulting to the local store instead of the daemon is wild behavior and it's better to just fix that instead imo
23:34:00
2 Jun 2024
@federicodschonborn:matrix.orgFederico Damián Schonborn changed their profile picture.00:25:40
@federicodschonborn:matrix.orgFederico Damián Schonborn changed their profile picture.00:28:10
@jade_:matrix.orgjade_
In reply to @ma27:nicht-so.sexy

yeah I only realized that because lazy me was doing sudo ./result/bin/nix to avoid changing my system's daemon %)

but, do you want me to submit a change going into that direction?
and regarding the change I'm currently working on, your suggestion is basically to just accept duplicated messages when "bypassing" the daemon on a remote build?

https://git.lix.systems/lix-project/lix/issues/18
00:34:33
@jade_:matrix.orgjade_
In reply to @artemist:mildlyfunctional.gay
Is there a plan to setup gerrit for lix-installer? I'm working on fixing the tests so I can do more development
we can set it up, that wouldn't be hard at all. we just don't have CI for it at the moment.
00:35:19

Show newer messages


Back to Room ListRoom Version: 10