!RROtHmAaQIkiJzJZZE:nixos.org

NixOS Infrastructure

378 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.114 Servers

Load older messages


SenderMessageTime
9 Feb 2026
@imincik:matrix.orgIvan Mincik (imincik) changed their profile picture.06:05:39
@k900:0upti.meK900Running an unstable-small eval for kernel 6.1908:17:53
@k900:0upti.meK900 @hexa (signing key rotation when) channel update failed, can you poke it? 09:49:51
@hexa:lossy.networkhexa (signing key rotation when)Hm?09:50:37
@k900:0upti.meK900update-nixos-unstable-small.service09:50:45
@k900:0upti.meK900Not sure why it failed09:50:48
@hexa:lossy.networkhexa (signing key rotation when)And yet no alert09:51:17
@hexa:lossy.networkhexa (signing key rotation when)Give me a minute09:51:33
@k900:0upti.meK900Maybe not processed yet09:51:42
@k900:0upti.meK900I'm just looking at grafana09:51:48
@hexa:lossy.networkhexa (signing key rotation when)
To https://github.com/NixOS/nixpkgs.git
 ! [remote rejected]           69ecaffa7deb4daa5a83cb813f8251665e3af93e -> nixos-unstable-small (Internal Server Error)
error: failed to push some refs to 'https://github.com/NixOS/nixpkgs.git'
Command failed with code (1) errno (0).
09:53:33
@hexa:lossy.networkhexa (signing key rotation when)it went through09:54:17
@k900:0upti.meK900Huh09:56:06
@hexa:lossy.networkhexa (signing key rotation when)after the restart09:56:28
@k900:0upti.meK900Oh09:56:32
@k900:0upti.meK900I thought it said internal error and went through anyway09:56:41
@k900:0upti.meK900https://www.githubstatus.com/incidents/ffz2k716tlhx10:03:32
@k900:0upti.meK900Github is on fire10:03:34
@k900:0upti.meK900AGAIN.10:03:36
@sinan:sinanmohd.comsinanmonitoring the situation 🍿11:54:02
10 Feb 2026
@dgrig:erethon.comdgrig

At some point in the past, a budget for https://tracker.security.nixos.org/ was approved by the foundation and the security tracker was deployed on a Hetzner Cloud project. We're still way below the budget limit, but we want to increase the size of the hosts (staging and prod) soon which will increase the cost and make it comparable to getting a dedicated host in Hetzner (for way more performance/€).

Is there a reason we should stay in Hetzner Cloud instead of getting a dedi? I vaguely remember someone (no idea who) saying back in late 2024 that Hetzner Cloud was easier to provision in terms of billing/permissions for the foundation and the infra team. Is this still true and a concern?

10:57:18
@vcunat:matrix.orgvcunat We do have dedicated Hetzner machines already (and added titan machine recently), so I wouldn't expect issues really. 11:11:22
@bot-wxt1221:matrix.orgBot_wxt1221图像.png
Download 图像.png
11:29:19
@bot-wxt1221:matrix.orgBot_wxt1221nixos wiki has something strange happened.11:29:28
@bot-wxt1221:matrix.orgBot_wxt1221Or where should I submit this stupid error.11:30:55
@bot-wxt1221:matrix.orgBot_wxt1221 * 11:30:59
@bot-wxt1221:matrix.orgBot_wxt1221Another thing is that it only happens when I refer to some website.11:38:13
@wegank:matrix.orgWeijiaSee https://github.com/NixOS/nixos-wiki-infra/issues/121.14:29:10
@bot-wxt1221:matrix.orgBot_wxt1221oh really stupid15:03:45
@hexa:lossy.networkhexa (signing key rotation when) #NixOS Wiki fwiw 15:06:37

There are no newer messages yet.


Back to Room ListRoom Version: 6