!RROtHmAaQIkiJzJZZE:nixos.org

NixOS Infrastructure

383 Members
Next Infra call: 2024-07-11, 18:00 CEST (UTC+2) | Infra operational issues backlog: https://github.com/orgs/NixOS/projects/52 | See #infra-alerts:nixos.org for real time alerts from Prometheus.116 Servers

Load older messages


SenderMessageTime
20 Jan 2025
@joerg:thalheim.ioMic92She was never there. But I dropped the email forwarding19:23:42
@hexa:lossy.networkhexai think she never accepted the invite fwiw19:35:53
@toonn:matrix.orgtoonn Would the invite still be valid? 20:17:49
@hexa:lossy.networkhexano20:22:14
@danielle:fairydust.spacedaniellehuh that wasn't on purpose but given that i can't find any creds in my 1password that seems accurate23:00:29
@danielle:fairydust.spacedanielle(sorry 🙈)23:00:44
@dgrig:erethon.comdgrig

(I've updated my availability for this week.)

If a team sync isn't possible this week, is there someone I can DM about me getting access to a host/VM or a Hetzner project so I can setup Grist as it's needed by NGI?

23:18:54
21 Jan 2025
@jfly:matrix.orgJeremy Fleischman (jfly)

I've also updated my availability for the week.

If you want to start chipping away at this before you have access to stuff, I think you could clone https://github.com/NixOS/infra, pick a non-critical infra machine (such as umbriel), and start adding Grist. I can give you a code review (I could even merge and deploy, but would want to wait for some guidance from more established members of the team before doing so)

00:27:59
@jfly:matrix.orgJeremy Fleischman (jfly)(that said, this'll be a lot easier for you if you get access to non-critical infra, which we need someone else to chime in on) 00:29:26
@dgrig:erethon.comdgrig I've got some questions about how we would want to handle the Grist installation in the first place, so I think it's best if we have that team sync first. I don't want to place extra burden on the team by spinning up something for review that will be thrown away if we want to setup Grist in a different way. 13:15:59
@jfly:matrix.orgJeremy Fleischman (jfly)sorry scheduling seems to be so difficult right now. happy to chat 1-1, but i'm so junior on the team i don't know that i'd be terribly helpful13:40:29
@rootname:matrix.org@rootname:matrix.org removed their display name rootname.19:55:14
@rootname:matrix.org@rootname:matrix.org left the room.19:59:59
22 Jan 2025
@hexa:lossy.networkhexaconfigured a silent-timeout on the linux builders after 2 hours22:10:38
21 Jan 2025
@oak:universumi.fioak 🏳️‍🌈♥️ changed their profile picture.22:35:13
22 Jan 2025
@hexa:lossy.networkhexathat might not be enough for some jobs, but we can bump that up as needed22:10:59
21 Jan 2025
@oak:universumi.fioak 🏳️‍🌈♥️ changed their profile picture.22:37:00
22 Jan 2025
@hexa:lossy.networkhexanot super happy about build slots being allocated for 2 days, when they're clearly stale22:11:30
23 Jan 2025
@paparodeo:matrix.org@paparodeo:matrix.org left the room.01:24:28
@dgrig:erethon.comdgrig

To keep everyone in the loop, I synced with Jeremy Fleischman (jfly) (thank you for your time and help!) about how to approach setting up Grist. For now I'll try to bring https://github.com/NixOS/nixpkgs/pull/305019 up to date and merged, so we can use it on non-critical infra easily.

I still have some open questions around authentication and SSO, object storage options, etc for when the next infra team sync takes place.

11:47:21
@k900:0upti.meK900 sleepy-brown is completely dead it seems 15:27:32
@k900:0upti.meK900No jobs running15:28:16
@hexa:lossy.networkhexacompletely idle 😄 15:28:21
@k900:0upti.meK900The machine seems to be up though15:28:23
@hexa:lossy.networkhexanix-daemon still alive15:28:33
@hexa:lossy.networkhexasshing works obv15:28:36
@hexa:lossy.networkhexa
Jan 23 10:19:25 sleepy-brown nix-daemon[2556787]: accepted connection from pid 3488928, user build (trusted)
Jan 23 10:20:40 sleepy-brown nix-daemon[2556787]: accepted connection from pid 3485125, user build (trusted)
Jan 23 10:39:18 sleepy-brown nix-daemon[2556787]: accepted connection from pid 3733722, user build (trusted)
Jan 23 11:12:15 sleepy-brown nix-daemon[2556787]: accepted connection from pid 4054631, user build (trusted)
Jan 23 11:19:11 sleepy-brown nix-daemon[2556787]: accepted connection from pid 4144888, user build (trusted)
Jan 23 11:29:25 sleepy-brown nix-daemon[2556787]: accepted connection from pid 47985, user build (trusted)
Jan 23 11:45:41 sleepy-brown nix-daemon[2556787]: accepted connection from pid 146057, user build (trusted)
Jan 23 12:13:05 sleepy-brown nix-daemon[2556787]: accepted connection from pid 349779, user build (trusted)
Jan 23 12:14:50 sleepy-brown nix-daemon[2556787]: accepted connection from pid 380056, user build (trusted)
Jan 23 14:56:25 sleepy-brown nix-daemon[2556787]: accepted connection from pid 1005320, user build (trusted)
15:28:48
@hexa:lossy.networkhexasus15:28:49
@hexa:lossy.networkhexano visible errors tbh15:30:38
@k900:0upti.meK900Nothing on the Hydra end either?15:30:54

Show newer messages


Back to Room ListRoom Version: 6