!RROtHmAaQIkiJzJZZE:nixos.org

NixOS Infrastructure

381 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
19 Feb 2026
@toonn:matrix.orgtoonn I'm not sure why you insist on the Nixpkgs write access. Repository access is not enough, "members: write" is an organization level permission. 17:39:39
@emilazy:matrix.orgemilyI am explaining that we already have a GitHub App hooked up to our GitHub Actions CI, and it already has write access to Nixpkgs, so the risk that a bot that can manage teams could lead to privilege escalation into Nixpkgs writes isn't any increase in the surface of the risk the app we already have already provides to our automation17:40:53
@toonn:matrix.orgtoonn Least priviledge would suggest having separate apps with strictly necessary permissions but storing multiple tokens in GitHub secrets means actions can access all of the permissions anyway. 17:41:23
@emilazy:matrix.orgemilythe reason "members: write" is dangerous is because it's equivalent to Nixpkgs commit access, nothing else you can do with it is remotely as risky17:41:52
@emilazy:matrix.orgemilyyou can offer different secrets to different workflows, but because of ^ I doubt it'd be that worthwhile. anyway, ideally it just uses team maintainership anyway. my point was only that it's not an increase in effective attack surface17:42:42
@toonn:matrix.orgtoonn The equivalence is useful to point out but I never tried to say it's a problem. 17:45:04
@toonn:matrix.orgtoonn I'm not sure team maintainership can be passed along through a token. 17:45:36
@gabyx:matrix.orggabyxIs rfc39 running currently?17:55:52
@toonn:matrix.orgtoonn AFAIK it is, new maintainers still get invites. Often they expire but then they come to the org owners room to ask for a new invite. 17:58:14
@hexa:lossy.networkhexa (signing key rotation when) all the time 18:14:22
@hexa:lossy.networkhexa (signing key rotation when)every 30 minutes18:14:35
@gabyx:matrix.orggabyxit only updates files in nixpkgs right? the maintainers file18:17:12
@hexa:lossy.networkhexa (signing key rotation when)no, it just issues team invites18:17:29
@hexa:lossy.networkhexa (signing key rotation when)https://discourse.nixos.org/t/garbage-collecting-cache-nixos-org/74249/10?u=hexa18:42:43
@hexa:lossy.networkhexa (signing key rotation when)We did the first garbage collection tonight, check the post for details!18:43:03
@dramforever:matrix.orgdramforeveri think it's not just me, but the post is completely inscrutable to me19:36:03
@dramforever:matrix.orgdramforeverso like, what does it mean?19:36:20
@dramforever:matrix.orgdramforeverif i try to get something that hasn't been [???] for 30 days from c.n.o it's ... gone?19:36:59
@jfly:matrix.orgJeremy Fleischman (jfly) A bunch of files have been "soft deleted". As far as you as a user of c.n. o is concerned, they're gone. The actual files will be removed from amazon's servers (and we will therefore stop paying for that storage) after 30 days. 19:46:30
@jfly:matrix.orgJeremy Fleischman (jfly) * 19:46:39
@jfly:matrix.orgJeremy Fleischman (jfly) (The benefit of doing it this way is we have 30 days to figure out if we did something wrong) 19:47:16
@hexa:lossy.networkhexa (signing key rotation when)
# zpool status
  pool: zroot
 state: DEGRADED
status: One or more devices have been removed.
	Sufficient replicas exist for the pool to continue functioning in a
	degraded state.
action: Online the device using zpool online' or replace the device with
	'zpool replace'.
  scan: scrub repaired 0B in 00:03:45 with 0 errors on Sun Feb  1 02:17:51 2026
config:

	NAME                                 STATE     READ WRITE CKSUM
	zroot                                DEGRADED     0     0     0
	  mirror-0                           DEGRADED     0     0     0
	    nvme-eui.002538b931005446-part3  ONLINE       0     0     0
	    nvme-eui.002538b931005449-part3  REMOVED      0     0     0

errors: No known data errors
20:12:45
@hexa:lossy.networkhexa (signing key rotation when)on pluto20:12:47
@hexa:lossy.networkhexa (signing key rotation when)collected debug logs, deconfigured the faulty disk and rebooted20:25:33
@hexa:lossy.networkhexa (signing key rotation when)sent a ticket for a replacement disk20:29:58
@hexa:lossy.networkhexa (signing key rotation when)the machine is back up and the disk was not enumerated20:30:17
@hexa:lossy.networkhexa (signing key rotation when)we got a new disk and resilvering is in progress22:20:08
@hexa:lossy.networkhexa (signing key rotation when)will finish in a minute or so22:21:43
@hexa:lossy.networkhexa (signing key rotation when)and a final reboot to check if everything comes up correctly22:29:52
@hexa:lossy.networkhexa (signing key rotation when)ok, looks good to me22:33:36

There are no newer messages yet.


Back to Room ListRoom Version: 6