<sb0>
whitequark: besides homu you have nothing running on lab.m-labs.hk, right?
<whitequark>
correct
<whitequark>
well, maybe there is something i do not remember. but then it is not important
jevinski_ has joined #m-labs
jevinskie has quit [Ping timeout: 245 seconds]
bb-m-labs has quit [Quit: buildmaster reconfigured: bot disconnecting]
<sb0>
of course, debian can't shut down properly...
<sb0>
whitequark: okay it's running on nixbld now, seems ok with ipv4, v6 should work after dns propagation
<whitequark>
ok
<sb0>
I also created you an account and added your ssh key
<whitequark>
ok, i can login
<sb0>
rjo: you have a tmux session running as the gitea account. did you something unusual and/or there is some kind of bug?
jevinskie has joined #m-labs
jevinski_ has quit [Ping timeout: 246 seconds]
<rjo>
sb0: that would surprise me. never touched gitea.
<rjo>
sb0: to use your preferred way of expressing it: looks like some nix shit again. typical.
<rjo>
same uid, as do astro and matterbridge
mumptai has joined #m-labs
<sb0>
well the thing is, there is no "again" since nixos bugs are actually quite rare
m4ssi has joined #m-labs
<rjo>
bullshit. you even reference nix bugs in the artiq manual.
<sb0>
there is one. with that uid thing (assuming this is indeed a nix bug) that makes two
<sb0>
considering all the other (often complex) things that work correctly, bugs are indeed rare
<rjo>
from what i can tell, considering the time you and others spent on nix so far already conda has been an acual time saver.
<rjo>
complexity and failure to get things working right is the thing that people complain about re nix.
<sb0>
it doesn't scale and it's not future proof. the new infra does many things that are not possible with conda.
<sb0>
plus many annoying things like removing packages manually from anaconda.org are no longer an issue
<sb0>
as it turns out, this uid problem is essentially user error
<sb0>
well, there is a small nixpkgs bug since it should have caught that problem but did not
<sb0>
rjo: can you log out so I can fix it cleanly?
key2_ is now known as key2
<mtrbot-ml>
[mattermost] <sb10q> @astro I just connected a ZC706 to nixbld
futarisIRCcloud has quit [Quit: Connection closed for inactivity]
urkk has joined #m-labs
futarisIRCcloud has joined #m-labs
urkk has quit [Ping timeout: 250 seconds]
kaaliakahn has quit [Ping timeout: 252 seconds]
remote_user__ has joined #m-labs
sb0 has quit [Quit: Leaving]
sb0 has joined #m-labs
<jfng1>
sb0: yes, minerva should work with caches disabled
<jfng1>
have you found issues with it ?
<jfng1>
currently, #30 makes ports name vary when minerva is instantiated with or without caches
<sb0>
jfng1: I was mostly confused because of #30
jevinskie has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
jevinskie has joined #m-labs
<mtrbot-ml>
[mattermost] <astro> sb10q: \o/
rohitksingh_work has quit [Read error: Connection reset by peer]
mumptai has quit [Ping timeout: 246 seconds]
mumptai has joined #m-labs
rohitksingh has joined #m-labs
<mtrbot-ml>
[mattermost] <sb10q> @astro as for cheaper alternatives to zc706, the Cora Z7-10 might be ok (dual core ARM) but the Cora Z7-07S (single core) definitely is not
<mtrbot-ml>
[mattermost] <sb10q> you'd get a XC7Z010, whereas the ZC706 has a XC7Z045