justanotheruser has quit [Ping timeout: 260 seconds]
tilpner has quit [Ping timeout: 260 seconds]
tilpner_ is now known as tilpner
alp has joined #nixos-dev
teto has quit [Ping timeout: 260 seconds]
alp has quit [Ping timeout: 272 seconds]
<JJJollyjim>
is anyone able to parse an actual error message out of this? I'm thinking "Killed signal terminated program" might mean it got cc1plus got oomkilled or something
Shados has quit [Read error: Connection reset by peer]
Shados has joined #nixos-dev
justanotheruser has joined #nixos-dev
rajivr has joined #nixos-dev
orivej has joined #nixos-dev
justanotheruser has quit [Ping timeout: 260 seconds]
cole-h has joined #nixos-dev
saschagrunert has joined #nixos-dev
niksnut has joined #nixos-dev
orivej has quit [Ping timeout: 256 seconds]
alp has joined #nixos-dev
orivej has joined #nixos-dev
orivej has quit [Ping timeout: 265 seconds]
alp has quit [Remote host closed the connection]
alp has joined #nixos-dev
cole-h has quit [Quit: Goodbye]
teto has joined #nixos-dev
teto has quit [Ping timeout: 260 seconds]
alp has quit [Ping timeout: 272 seconds]
teto has joined #nixos-dev
tokudan has quit [Remote host closed the connection]
alp has joined #nixos-dev
tokudan has joined #nixos-dev
tokudan has quit [Remote host closed the connection]
tokudan has joined #nixos-dev
<julm>
has anyone ever got a fancy number like that returned by nix-collect-garbage? note: currently hard linking saves 17592186044414.87 MiB
<immae>
It happened to someone else a few weeks ago if I remember correctly
<Mic92>
julm: yes, this seems to be an overflow
<julm>
immae: ok. by the way, it's 0xffffffffffe
<immae>
the positive side is that now you’ll probably never run out of space on your disk :p
<Mic92>
Not necessarly Nix still could re
<Mic92>
require more storage than this
<JJJollyjim>
is anyone aware of a good way to detect whether you're running in a nix sandbox?
<JJJollyjim>
(on linux specifically)
<JJJollyjim>
this program wants to sandbox itself, and that doesn't work under the nix build sandbox. That's fine, I can patch out the self-sandboxing, but I don't want to leave a security hole if it's run on a non-daemon install
<JJJollyjim>
(or run outside a nix build, which could realistically happen in this case)
<clever>
JJJollyjim: $NIX_BUILD_TOP points to the temdir that the build is occuring within
<clever>
and it shouldnt be set outside of a build (and probably nix-shell)
alp has quit [Ping timeout: 272 seconds]
spacekookie has quit [Quit: **aggressive swooshing**]
<stigo>
merged it - ticked all boxes and works ok.
<ghuntley>
bouncing an idea here, would folx find it an expression to build a windows 10 virtual machine w/native windows 10 openssh enabled + ssh keys installed?
Raito_Bezarius has quit [Remote host closed the connection]
Raito_Bezarius has joined #nixos-dev
<ghuntley>
create windows10 vm that has openssh server enabled that one can then with a client ssh into.
<ghuntley>
Cool things that could happen: a) enable developer mode/install wsl distro b) execute commands in wsl c) nix inception
Raito_Bezarius has quit [Remote host closed the connection]
Raito_Bezarius has joined #nixos-dev
<gchristensen>
that sounds cool
kloenk has quit [Quit: WeeChat 2.9]
<abathur>
anyone aware of lucid big-picture discussion/documentation on the use-cases/purposes of the experimental nix dev-shell/develop, shell, and run commands, and how existing nix-shell practices/use-cases should map over? I've seen the nix command pages on nixos.wiki, but I'm not sure I grok the vision
justanotheruser has joined #nixos-dev
NinjaTrappeur1 has joined #nixos-dev
leungbk has joined #nixos-dev
NinjaTrappeur1 has quit [Client Quit]
NinjaTrappeur has quit [Quit: WeeChat 2.8]
leungbk has quit [Remote host closed the connection]
NinjaTrappeur has joined #nixos-dev
RaitoBezarius has joined #nixos-dev
RaitoBezarius has quit [Client Quit]
Raito_Bezarius has quit [Quit: quit()]
Raito_Bezarius has joined #nixos-dev
rycee1 is now known as rycee
Raito_Bezarius has quit [Client Quit]
Raito_Bezarius has joined #nixos-dev
ris has joined #nixos-dev
teto has quit [Ping timeout: 240 seconds]
rajivr has quit [Quit: Connection closed for inactivity]
orivej has joined #nixos-dev
alp has quit [Ping timeout: 272 seconds]
cole-h has joined #nixos-dev
hax404 has joined #nixos-dev
<hexa->
ma27[m]: do you also have the issue that matrix-synapse is hogging a whole cpu core, probably presence related? me and maralorn are affected by this every once in a while, like now.
maralorn has joined #nixos-dev
<hexa->
I was wondering if moving to a worker based setup might mitigate some of this
<ma27[m]>
afaics no, haven't seen that
<V>
hexa-: sounds like that's just matrix-synapse :p
NinjaTrappeur has quit [Ping timeout: 240 seconds]
<hexa->
sure, massive json over https in python is not expected to be fast
<hexa->
we're packaging conduit right now
<hexa->
but that (conduit itself) is not quite there yet
<V>
ye
NinjaTrappeur has joined #nixos-dev
Raito_Bezarius has quit [Remote host closed the connection]
Raito_Bezarius has joined #nixos-dev
__monty__ has joined #nixos-dev
bennofs_ has joined #nixos-dev
bennofs has quit [Ping timeout: 240 seconds]
__Sander__ has joined #nixos-dev
Raito_Bezarius has quit [Quit: WeeChat 2.9]
Raito_Bezarius has joined #nixos-dev
alp has joined #nixos-dev
<gchristensen>
did somebod ymerge a PR to the nixos-20.09 branch?
<samueldr>
(and unless you changed something, that only PR opened against nixos-20.09 has "Merging is blocked" here)
<gchristensen>
it looks like a commit was pushed to nixos-20.09 or something
<gchristensen>
"Updates were rejected because a pushed branch tip is behind its remote" while ! [rejected] ba0bd29a1aef66a67b50f377413b05ae402f4fc3 -> nixos-20.09 (non-fast-forward)
<sphalerite>
gchristensen: is https://logs.nix.ci/?key=nixos/nixpkgs.93675&attempt_id=926ef1bf-dc04-41bb-b837-9714a23836a2 a known ofborg issue, or do you have any idea what's going on here?
<gchristensen>
I have no idea, sorry
<gchristensen>
my brain is at 20% capacity these days, and it is a struggle to get dayjobwork done much less keeping up here :(
<worldofpeace>
" You’re not authorized to merge this pull request. "
<samueldr>
at least the bot hasn't been clued in to a push to that branch
<cole-h>
Weird o_O
<samueldr>
gchristensen: revision id of your tip of nixos-20.09?
<worldofpeace>
I'm kinda having similar problems as graham, I really probably need to be helping out with ZHF and Jon with RM stuff (we just did beta today we're actually due to release at the end of the week...) I know we don't "owe" anyone a timely release but it's hard with how many "spoons" I have. Just want to mention this because I think our new RM needs more support, maybe I should share our targeted upcoming outcomes.
<cole-h>
How can I help?
NinjaTrappeur has quit [Quit: WeeChat 2.9]
NinjaTrappeur has joined #nixos-dev
<worldofpeace>
cole-h: ZHF. The target for the "end of it" was the 25th, these were obviously very very ambitious targets since this realistically wasn't going to be done in a month. (I believe I talked about a while ago where there could be a ZHF "triage team", or just some sort of supplemental "engineering" group for the release). Anyways, you would be able to help maximally if you could merge PRs... Not sure if you're ready for
<worldofpeace>
that, but approving and finding someone to work with to get them merged would help with the outcome "ZHF is doing well"
<worldofpeace>
You've also be very helpful tracking down blocking issues and making PRs
<cole-h>
In addition to reviewing 20.09-targeted PRs, is more help needed for some of the "To Do"s on the "20.09 Blockers" project?
<cole-h>
It looks like 3 of those are tracking/waiting for the release itself, but 5 of them look decently actionable.
<worldofpeace>
There probably needs to be a lot more reviewing of issues because I think there's probably more blockers that need to be added to the milestone and project
<worldofpeace>
I think, atm, that job has been solely up to the RM to label them, which isn't good
<cole-h>
I think adding to a project needs committer, but I can do milestones at least.
<cole-h>
committer permissions*
<immae>
may I suggest that maybe not making it extra difficult for external people to help would maybe help reaching the target? (as far as I am concerned I was quite motivated to help for this release and I gave up because I couldn’t properly poke the release team for PR’s)
<immae>
(well to be totally honest I sent an e-mail to get that permission and then waited and then forgot to get back to it in absence of answer)
<worldofpeace>
We should probably have a release management issue with "need blocker bug process and criteria", along with a release criteria... there's soo many things, I'd say RM is probably the most difficult job atm for someone with an overactive brain like me :D
<worldofpeace>
immae: hmm, do you mean you're not a part of the maintainers team still?
<immae>
nope
<immae>
I sent an e-mail asking for it a few weeks ago and got no answer
<immae>
(and then I went to other things and forgot)
<cole-h>
So, IME, the Big 3 are: 1) reviewing/merging 20.09 PRs; 2) triaging issues as blockers for the release (adding to the milestone or project if permitted); and 3) resolving said blockers. Would you agree, worldofpeace?
<worldofpeace>
immae: oh, so you sent an email asking to be a part of that team. IIRC it's an automated thingy, but maybe it can be manual as well. Was this email to me or Jon?
<cole-h>
I think the automated invites stopped a while back, since there's no way to "blacklist" people who've rejected the invite
<worldofpeace>
cole-h: essentially, and the last one is blocker review meetings so this can be done proactively
<immae>
I sent to gchristensen zimbatm domen and edolstra (as suggested by ryantm on this channel)
<immae>
So you were not on the list sorry :/
<worldofpeace>
Ah okay, I wouldn't have been able to add u anyways (I think)
<worldofpeace>
I think Jon will be able to organize the go/no-go meetings since I have really great notes on that, so that at least I'm thankful for my past self 😸
<immae>
(I admit I have no way to check that, I have no access to any information from the nixos organization :p )
<ryantm>
It would be nice to expand who can manage that team, if we are not going to be automatically adding people for a while.
<cole-h>
Unfortunately, I think it requires owner permissions on the org?
<worldofpeace>
I've added to the ZHF issue "If you're unable to because you're not a member of the NixOS org please ping
<worldofpeace>
@jonringer and @worldofpeace (the same people in the team)."
<immae>
Ah that’s good enough I guess :)
<cole-h>
worldofpeace: I think a general releng team would be a nice addition to delegate to.
<immae>
Thanks for the addition!
<cole-h>
I don't know of a good split for responsibilities between the RM and releng teams (if it were added), though.
<worldofpeace>
ryantm: I think it should then be like nixpkgs-committers should be able to manage invites, I'm not sure if github is flexible like that though
<worldofpeace>
cole-h: atm RM's are also release engineers :D
<cole-h>
"Only organization owners can invite users to join an organization. "
<worldofpeace>
wah
<cole-h>
So doesn't seem possible, unless more owners are added.
<gchristensen>
maybe patching the rfc39 repo to store already-invited people in a database of some sort
<cole-h>
worldofpeace: Right, but I meant more of a split. I was thinking RMs would focus on triaging blockers, while releng would attempt to unblock those and merge PRs, etc?
<cole-h>
This kind of coordination is outside my wheelhouse, though.
<worldofpeace>
come thru rust hackers 🤓
<worldofpeace>
cole-h: yeah, I think it's really hard to establish new things at the same time as having to actively "do the thing". Typically things go down like this anyway
<worldofpeace>
Is there in an issue in nixpkgs about the issue with rfc39 rn?
<{^_^}>
nix#3427 (by ChrisJefferson, 26 weeks ago, closed): Stop inviting me to the NixOS github organisation
<worldofpeace>
oh cole-h. I think there should at least be an issue in nixpkgs that invites to maintainers isn't going on anymore, why, how we could fix it
<{^_^}>
rfc39#3 (by cole-h, 22 seconds ago, open): Create a database of already-invited users and don't invite them again
<worldofpeace>
cole-h: thanks
<gchristensen>
fwiw, with how little I sleep and how little time I have, I should be assumed to be pretty much useless for a good while. I'm sorry :(
<cole-h>
gchristensen++ Take care of yourself.
<{^_^}>
gchristensen's karma got increased to 341
<worldofpeace>
gchristensen: I recommend updating your github status with that maybe 😸 that has helped me get the point across in the past "I've been on three different planes and two hours of sleep"
<gchristensen>
done
<worldofpeace>
life happens, I guess what matters is that you can carry on gracefully (as you can) and I wish u the best sleep ❤️
<cole-h>
gchristensen: tbh I'd also add "0 free time cya" -- the meaning of the "yellow color" isn't immediately obvious
<cole-h>
:P
<gchristensen>
done
<cole-h>
Love it.
<immae>
(just to make it explicit: I’m not blaming anyone here, I suppose most people here are doing all that "for free" - and so am I -. I’m just trying to help maybe adjustthe process to make contributions a bit more fluid considering my own experience)
<worldofpeace>
immae: yep, I think I understand where you're coming from. Often it can be hard for not feel like "welp this kinda is because of me" because you can develop a tendency to want to push yourself without remembering that you don't want to push yourself off a cliff :D
taktoa[c] has quit [Ping timeout: 244 seconds]
elvishjerricco has quit [Ping timeout: 244 seconds]
gleber has quit [Ping timeout: 246 seconds]
srhb has quit [Ping timeout: 258 seconds]
dmj` has quit [Ping timeout: 240 seconds]
johanot has quit [Ping timeout: 244 seconds]
nh2 has quit [Ping timeout: 244 seconds]
emilazy has quit [Ping timeout: 260 seconds]
ghuntley has quit [Ping timeout: 260 seconds]
cstrahan has quit [Ping timeout: 244 seconds]
sdier has quit [Ping timeout: 260 seconds]
cbarrett has quit [Ping timeout: 260 seconds]
jkkm has quit [Ping timeout: 260 seconds]
manveru has quit [Ping timeout: 260 seconds]
carter has quit [Ping timeout: 244 seconds]
betawaffle has quit [Ping timeout: 260 seconds]
mdlayher has quit [Ping timeout: 260 seconds]
angerman has quit [Ping timeout: 260 seconds]
teehemkay has quit [Ping timeout: 260 seconds]
teehemkay has joined #nixos-dev
jkkm has joined #nixos-dev
srhb has joined #nixos-dev
<immae>
yes :)
cstrahan has joined #nixos-dev
cbarrett has joined #nixos-dev
mdlayher has joined #nixos-dev
emilazy has joined #nixos-dev
manveru has joined #nixos-dev
carter has joined #nixos-dev
johanot has joined #nixos-dev
elvishjerricco has joined #nixos-dev
sdier has joined #nixos-dev
angerman has joined #nixos-dev
betawaffle has joined #nixos-dev
taktoa[c] has joined #nixos-dev
nh2 has joined #nixos-dev
dmj` has joined #nixos-dev
ghuntley has joined #nixos-dev
gleber has joined #nixos-dev
Raito_Bezarius has quit [Remote host closed the connection]
Raito_Bezarius has joined #nixos-dev
Raito_Bezarius has quit [Client Quit]
Raito_Bezarius has joined #nixos-dev
Raito_Bezarius has quit [Quit: WeeChat 2.9]
Raito_Bezarius has joined #nixos-dev
Raito_Bezarius has quit [Client Quit]
Raito_Bezarius has joined #nixos-dev
Raito_Bezarius has quit [Remote host closed the connection]
Raito_Bezarius has joined #nixos-dev
Raito_Bezarius has quit [Client Quit]
Raito_Bezarius has joined #nixos-dev
Raito_Bezarius has quit [Quit: WeeChat 2.9]
erictapen has joined #nixos-dev
Raito_Bezarius has joined #nixos-dev
__monty__ has quit [Quit: leaving]
__Sander__ has quit [Quit: Konversation terminated!]
niksnut has quit [Ping timeout: 256 seconds]
manveru has quit [Ping timeout: 240 seconds]
feepo has quit [Ping timeout: 244 seconds]
prusnak has quit [Ping timeout: 244 seconds]
kalbasit has quit [Ping timeout: 244 seconds]
davidtwco has quit [Ping timeout: 244 seconds]
sorear has quit [Read error: Connection reset by peer]
c00w has quit [Ping timeout: 240 seconds]
ghuntley has quit [Ping timeout: 240 seconds]
teehemkay has quit [Ping timeout: 240 seconds]
thoughtpolice has quit [Read error: Connection reset by peer]
alunduil has quit [Ping timeout: 240 seconds]
johanot has quit [Ping timeout: 260 seconds]
sdier has quit [Ping timeout: 260 seconds]
emilazy has quit [Ping timeout: 260 seconds]
georgyo has quit [Ping timeout: 260 seconds]
carter has quit [Ping timeout: 260 seconds]
mdlayher has quit [Ping timeout: 260 seconds]
betawaffle has quit [Ping timeout: 260 seconds]
cstrahan has quit [Ping timeout: 260 seconds]
angerman has quit [Ping timeout: 260 seconds]
jkkm has quit [Ping timeout: 260 seconds]
sorear has joined #nixos-dev
elvishjerricco has quit [Ping timeout: 272 seconds]