gchristensen changed the topic of #nixos-borg to: https://www.patreon.com/ofborg https://monitoring.nix.ci/dashboard/db/ofborg?refresh=10s&orgId=1&from=now-1h&to=now "I get to skip reviewing the PHP code and just wait until it is rewritten in something sane, like POSIX shell. || https://logs.nix.samueldr.com/nixos-borg
<samueldr> !m is a botbot thing!
<samueldr> (which can now be replaced by the more gamified and quantifiable ++
<gchristensen> > builtins.readFile /etc/passwd
<{^_^}> access to path '/etc/passwd' is forbidden in restricted mode
<samueldr> ah, gchristensen, there were strong tentatives in #bottest the oteher day
<samueldr> gchristensen++
<{^_^}> gchristensen's karma got increased to 2
<gchristensen> neat
<samueldr> AFAIK, the only issue with the implementation is how it will gobble up memory and cpu cycles, which could cause low-levels DoS in how it is ran
<gchristensen> > r
<{^_^}> undefined variable 'r' at (string):31:9
<samueldr> there's some kind of per-channel namespacing
<samueldr> and private messages too
<samueldr> and you can decrease your karma
<samueldr> samueldr++
<{^_^}> samueldr's karma got decreased to -1
<samueldr> (I've been following the progress, looks like a fun thing)
<infinisil> gchristensen: I have a set a cgroups limit of 100MB memory and 50% CPU :)
<infinisil> or 200MB, can't remember
<infinisil> It still can eat all the swap, but I don't know how I could prevent that
<infinisil> samueldr++
<{^_^}> samueldr's karma got increased to 0
<infinisil> samueldr++
<{^_^}> samueldr's karma got increased to 1
<infinisil> For your sacrifice :P
<samueldr> :3
<samueldr> oh, so if the nix subprocess b0rks, the whole bot is killed?
<infinisil> Why would it?
<infinisil> cgroups doesn't kill anything, it just limits it
<infinisil> almost as if there actually was only 100M and half the CPU power
<infinisil> as far as i know at least
<samueldr> oh
<samueldr> neater
<samueldr> I thought it would work with the OOM thing
<infinisil> the out-of-memory thing being?
<infinisil> Ah just killing it i assume
<samueldr> yeah, the oom killer of the kernel
<samueldr> > Specify the absolute limit on memory usage of the executed processes in this unit. If memory usage cannot be contained under the limit, out-of-memory killer is invoked inside the unit.
<{^_^}> error: syntax error, unexpected IN, expecting ')', at (string):31:78
<samueldr> oh, quoting text is going to be... more painful
<infinisil> Oh..
<infinisil> It should say "This doesn't look like nix at all!"
<samueldr> I must be the only one who does that, otherwise it would have been noticed
<infinisil> Nah I'd also quote with >
<samueldr> maybe >> to nix?
<infinisil> Meh, the very rare annoyance of an unexpected error message isn't worth it imo
<gchristensen> I disagree
<samueldr> I, too, would tend to say that that kind of noise would be grinding, just like, uh, PR merge taking three messages *says he shamefully*
<gchristensen> there are hundreds of cases of messages starting with a >
<infinisil> #haskell also uses > as a prefix for their eval bot and I haven't seen anybody complain
<infinisil> And I think some time ago an idris bot was working in #idris which used > too
gchristensen has left #nixos-borg ["WeeChat 1.9.1"]
gchristensen has joined #nixos-borg
<gchristensen> >.>
<{^_^}> error: syntax error, unexpected '.', at (string):31:9
<infinisil> Alright, looking through my logs, I found 8 instances in April of people using `> ` as a prefix for their messages
<gchristensen> the prefix isn't > :)
<infinisil> Huh?
<gchristensen> the prefix isn't `> `
<infinisil> Yeah I can change it to `> `, which should eliminate all those >.<
<infinisil> Oh #zsh is also using the > prefix
<infinisil> #bash is using #
<samueldr> what's the most nix-like sign?
<samueldr> the function call operator?
<samueldr> ( )
<infinisil> sign?
<infinisil> You mean on what nix can be recognized?
<samueldr> yeah
<samueldr> (and the space was a joke!)
<infinisil> Heh yeah
<samueldr> : (when spaced) defines functions, would ": " cause issues?
<infinisil> > { x ? 10, y }: text: "${text}: ${toString (x + y)}"
<{^_^}> <LAMBDA>
<infinisil> This is very nixy and couldn't be another language :P
<infinisil> Hmm
<infinisil> Every repl uses >, that's why it's so nice
<infinisil> and fitting
<infinisil> haha, how about ${
<infinisil> ${1 + 1}
<infinisil> >1+1
<infinisil> Alright I changed it to only trigger on "> " for now
<infinisil> > 1+1
<infinisil> Or not at all!
<infinisil> Um gchristensen it's happening right now
<infinisil> Oh wait
<infinisil> maybe not, disregard
<infinisil> > "it just took a while to start"
<{^_^}> "it just took a while to start"
<infinisil> I'll go to bed, good night :2
<infinisil> >.<
<gchristensen> > builtins.exec "echo hi"
<{^_^}> attribute 'exec' missing, at (string):31:9
jtojnar has quit [Ping timeout: 248 seconds]
jtojnar has joined #nixos-borg
cransom has joined #nixos-borg
orivej_ has quit [Ping timeout: 250 seconds]
MichaelRaskin has quit [Quit: MichaelRaskin]
FRidh has joined #nixos-borg
orivej has joined #nixos-borg
FRidh has quit [Read error: Connection reset by peer]
FRidh has joined #nixos-borg
Dezgeg has joined #nixos-borg
<Mic92_> > ?
<{^_^}> error: syntax error, unexpected '?', at (string):31:9
<makefu> > x = 1+1
<{^_^}> x defined
<makefu> > x
<{^_^}> 2
<infinisil> gchristensen: My bot randomly exited today at 17:18:23 (1:30h ago)
<infinisil> I haven't added more logging messages, i don't have any more descriptive error, just this time :
<infinisil> )
MichaelRaskin has joined #nixos-borg
FRidh has quit [Quit: Konversation terminated!]
Dezgeg has quit [Ping timeout: 246 seconds]
Dezgeg has joined #nixos-borg
LnL has quit [Ping timeout: 248 seconds]
LnL has joined #nixos-borg
<{^_^}> [ofborg] @grahamc pushed 32 commits to released: https://git.io/vpXu2
<{^_^}> → 5fb2d054 by @grahamc: Merge pull request #150 from ryantm/patch-1
<{^_^}> → 3f0e68c2 by @ryantm: add r-ryantm to trusted users
<{^_^}> → f6172c84 by @obadz: add obadz to trusted users
<{^_^}> [ofborg] @grahamc pushed 2 commits to released: https://git.io/vpV2a
<{^_^}> → 38b26e65 by @grahamc: Merge pull request #172 from Ekleog/default-nix-2
<{^_^}> → aeaf93b9 by @Ekleog: Default to building with nix2
<{^_^}> [ofborg] @grahamc merged pull request #174 → Add myself to config.extra-known-users → https://git.io/vpKRy
<{^_^}> [ofborg] @grahamc pushed 2 commits to released: https://git.io/vpXur
<{^_^}> → b9edcead by @Synthetica9: Add myself to config.extra-known-users
<{^_^}> → 6c4aa422 by @grahamc: Merge pull request #174 from Synthetica9/patch-1
<{^_^}> [ofborg] @grahamc pushed 2 commits to released: https://git.io/vpXu6
<{^_^}> → 3ba7d259 by @knedlsepp: Add knedlsepp to config.extra-known-users
<{^_^}> → 0915000e by @grahamc: Merge pull request #173 from knedlsepp/add-knedlsepp
<{^_^}> [ofborg] @grahamc merged pull request #173 → Add knedlsepp to config.extra-known-users → https://git.io/vpr1J
<{^_^}> [ofborg] @grahamc pushed 4 commits to next: https://git.io/vpXu1
<{^_^}> → d473806f by @Ekleog: Add nom dependency
<{^_^}> → 0c1b07c3 by @Ekleog: Simplify `parse` function using `flat_map`
<{^_^}> [ofborg] @grahamc merged pull request #124 → Nom → https://git.io/vpXuM
<{^_^}> → 206f1556 by @Ekleog: Use nom as the comment parser
<{^_^}> [ofborg] @grahamc pushed 5 commits to released: https://git.io/vpXuF
<{^_^}> → d473806f by @Ekleog: Add nom dependency
<{^_^}> → 0c1b07c3 by @Ekleog: Simplify `parse` function using `flat_map`
<{^_^}> → 206f1556 by @Ekleog: Use nom as the comment parser
<gchristensen> ok so this might be a horrible plan
<infinisil> Hmm?
<gchristensen> well I have nixops automatically doing a deploys
<gchristensen> from a git repo
<gchristensen> I should almost certainly stage it out, so it deploys to core-0 then core-1 then core-2 and then all
<gchristensen> but core-1 and core-2 don't exist yet :
<gchristensen> :P
<MichaelRaskin> Maybe even double-deploy to some target to check that deployments are not fully broken…
<MichaelRaskin> Ah ouch
<gchristensen> yeah, that is especially painful as an OS upgrade on core-0 takes out ofborg for the duration, since it is the only rabbitmq node
<MichaelRaskin> Oh
<gchristensen> in the past I've handled that in ways