!RROtHmAaQIkiJzJZZE:nixos.org

NixOS Infrastructure

395 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.119 Servers

You have reached the beginning of time (for this room).


SenderMessageTime
14 Jul 2025
@hexa:lossy.networkhexahttps://github.com/NixOS/nixos-status/commits/main/15:43:07
@hexa:lossy.networkhexaI 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.networkhexaPolling it in reasonable intervals is fine16:21:43
@hexa:lossy.networkhexaIdeally 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.networkhexait is a public api 🤷16:24:15
@hexa:lossy.networkhexaprom16:24:23
@relichunter:nitro.chatrelichunter joined the room.18:52:52

Show newer messages


Back to Room ListRoom Version: 6