!RROtHmAaQIkiJzJZZE:nixos.org

NixOS Infrastructure

390 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.120 Servers

Load older messages


SenderMessageTime
17 Feb 2025
@hexa:lossy.networkhexacool, have to debug why nix doesn't like my colmena flake anymore first 🙂 00:28:17
@hexa:lossy.networkhexahttps://github.com/zhaofengli/colmena/issues/25900:28:57
@hexa:lossy.networkhexaok00:46:54
@hexa:lossy.networkhexaok, start an eval and will check back tomorrow01:02:35
@hexa:lossy.networkhexa* ok, started an eval and will check back tomorrow01:02:39
@Ericson2314:matrix.orgJohn Ericson oh sheesh sorry not sure how i missed that you replied right away! 05:14:41
@Ericson2314:matrix.orgJohn Ericson OK, fingers crossed! 05:15:12
@joerg:thalheim.ioMic92ok with me.06:22:14
@joerg:thalheim.ioMic92Maybe some sort of use-after-free?06:23:17
@joerg:thalheim.ioMic92 hexa (signing key rotation when): forwarded this crash to nan for inspection. 06:28:07
@joerg:thalheim.ioMic92Revert doesn't sound like a bad call. The code looks dangerous.06:56:11
@hexa:lossy.networkhexawas fixed by this commit10:04:07
@hexa:lossy.networkhexano crashes since10:04:26
@hexa:lossy.networkhexalooked fine, will give the staging folks some time to finish up and then deploy the update15:48:58
@Ericson2314:matrix.orgJohn Ericson hexa (signing key rotation when): OK sweet! 15:50:42
@Ericson2314:matrix.orgJohn Ericson I have some code using more LegacySSHStore too 15:51:12
@Ericson2314:matrix.orgJohn Ericsonnow, on one hand it does potentially sketch things with temp roots15:51:25
@Ericson2314:matrix.orgJohn Ericsonbut on the other hand, the current use of temp roots is also wrong15:51:34
@Ericson2314:matrix.orgJohn Ericsonso 🤷15:51:39
@hexa:lossy.networkhexatemp roots?15:55:50
18 Feb 2025
@dgrig:erethon.comdgrig hexa (signing key rotation when) Jonas Chevalier Mic92 (sorry for the direct ping) The Nix@NGI team needs to send some emails from the ngi@nixos.org email address to ~500 recipients. Last time this team needed something done from improvmx, the request was completed in an ad-hoc manner and I'm wondering if there's a way to formalize this. Either if someone from the Nix@NGI team had access to improvmx so we can send emails ourselves or if there's a better way to ask for someone with access to do the email sending for us. If this room isn't the proper avenue to discuss this please let me know where you think it's more appropriate to have this discussion (nixos/org maybe?) 11:18:16
@zimbatm:numtide.comJonas Chevalier @jfly:matrix.org is probably the best person to talk to about this 12:14:50
@hexa:lossy.networkhexaOur improvmx does support sender accounts, so we can set this up12:49:24
@hexa:lossy.networkhexa* Our improvmx account does support sender accounts, so we can set this up12:49:29
@joerg:thalheim.ioMic92Improvemx has a daily quota and this is below the quota13:06:37
@hexa:lossy.networkhexait says 600/mo for the subscription we have, where does it expose a daily quota?13:14:31
@hexa:lossy.networkhexa* it says 6000/mo for the subscription we have, where does it expose a daily quota?13:14:36
@dgrig:erethon.comdgrig Even if it has a daily limit, I think we're ok with sending emails in 2-3 batches if that would help with any daily quotas. Can we get a sender account created with the owner being ngi@nixos.org and a sending address of ngi@nixos.org? I understand that this specific address already exists and is a mailing list in improvmx. 13:19:02
@hexa:lossy.networkhexaomw13:20:40
@hexa:lossy.networkhexaok, created the account and added the credentials to the ngi collection on bitwarden13:22:40

Show newer messages


Back to Room ListRoom Version: 6