!RROtHmAaQIkiJzJZZE:nixos.org

NixOS Infrastructure

352 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.109 Servers

Load older messages


SenderMessageTime
14 Jul 2025
@hexa:lossy.networkhexa (signing key rotation when)by all means, help.07:40:47
@hexa:lossy.networkhexa (signing key rotation when)I can't answer why mail delivery doesn't work however.07:41:16
@hexa:lossy.networkhexa (signing key rotation when)especially since you've given two different mail providers now07:42:02
@ctheune:matrix.flyingcircus.ioChristian Theune hexa (signing key rotation when): alright, will look into it 07:42:53
@hexa:lossy.networkhexa (signing key rotation when) Christian Theune: the last mail I've received is from July 3rd btw 07:42:53
@hexa:lossy.networkhexa (signing key rotation when)I run in mailing list mode07:43:00
@shock-wave:matrix.orgshock-waveIt was working as of 2nd of july for me.07:43:14
@ctheune:matrix.flyingcircus.ioChristian Theuneaha! 07:43:19
@ctheune:matrix.flyingcircus.ioChristian Theunemaybe that's a more widespread issue, i'll have a colleague look into it07:43:41
@ctheune:matrix.flyingcircus.ioChristian Theunei made an internal ticket and pointed the colleague back here.07:44:58
@k900:0upti.meK900image.png
Download image.png
15:36:19
@k900:0upti.meK900Whomst broke status.n.o15:36:24
@hexa:lossy.networkhexa (signing key rotation when)what am I missing?15:40:23
@k900:0upti.meK900It's not centered15:41:23
@hexa:lossy.networkhexa (signing key rotation when)https://github.com/NixOS/nixos-status/commits/main/15:43:07
@hexa:lossy.networkhexa (signing key rotation when)I have a suspicion15:43:10
@zhaofeng:zhaofeng.liZhaofeng Li (from #users:nixos.org ) What's the best/most police way to get the history of channel bumps these days? Is listing the nix-releases bucket polite enough? https://status.nixos.org queries https://prometheus.nixos.org which I presume is not intended to be consumed by others 16:20:49
@zhaofeng:zhaofeng.liZhaofeng Li * (from #users:nixos.org ) What's the best/most polite way to get the history of channel bumps these days? Is listing the nix-releases bucket polite enough? https://status.nixos.org queries https://prometheus.nixos.org which I presume is not intended to be consumed by others 16:21:19
@hexa:lossy.networkhexa (signing key rotation when)Polling it in reasonable intervals is fine16:21:43
@hexa:lossy.networkhexa (signing key rotation when)Ideally we'd have a pubsub service16:22:55
@zhaofeng:zhaofeng.liZhaofeng LiYou mean listing the bucket?16:23:33
@zhaofeng:zhaofeng.liZhaofeng Li* You mean listing the bucket? I can cook up some promql, but that feels a bit awkward16:24:00
@hexa:lossy.networkhexa (signing key rotation when)it is a public api 🤷16:24:15
@hexa:lossy.networkhexa (signing key rotation when)prom16:24:23
@relichunter:nitro.chatrelichunter joined the room.18:52:52
@arianvp:matrix.orgArianhttps://releases.nixos.org/?prefix=nixpkgs/ Shows all channel bumps 19:36:36
@dramforever:matrix.orgdramforeverit's a little bit annoying19:37:24
@dramforever:matrix.orgdramforeverthat page is just a javascript that pulls from s319:37:34
@arianvp:matrix.orgArianVisiting that website literally equivalent to listing the bucket iirc . I think the cost here is neglibile and you can probably just do listBucket on the bucket directly?19:37:46
@dramforever:matrix.orgdramforeveryeah just use your favorite s3 library19:38:35

Show newer messages


Back to Room ListRoom Version: 6