!RROtHmAaQIkiJzJZZE:nixos.org

NixOS Infrastructure

379 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.117 Servers

Load older messages


SenderMessageTime
22 Sep 2025
@ghpzin:envs.netghpzin Metrics are still there, dashboard hardcodes instance="monitoring.nixos.org:9200" 17:15:55
@vcunat:matrix.orgVladimír ČunátI think I fixed the graphs now.17:16:37
@vcunat:matrix.orgVladimír ČunátJust edited the dashboard.17:17:02
@sternenseemann:systemli.orgsterni Do any (Darwin) builders use Nix 2.30 already? We've noticed the interesting problem that the new build-dir location causes longer paths which can relatively easily cause failures becasue unix socket paths are quite restricted on macOS apparently. (Observed with `haskellPackages.network.) 19:50:07
@emilazy:matrix.orgemilyIIRC this was mitigated in the latest patch release19:50:54
@emilazy:matrix.orgemilywith possible further changes to come19:51:07
@emilazy:matrix.orgemily(the limits are similarly strict on Linux btw, just the sandbox helps there)19:51:21
@hexa:lossy.networkhexano, they track nixos-stable19:51:33
@hexa:lossy.networkhexa* no, they track nixpkgs-stable19:51:36
@sternenseemann:systemli.orgsternihttps://github.com/NixOS/nix/pull/13839?19:51:40
@hexa:lossy.networkhexaso 2.28ish19:51:41
@hexa:lossy.networkhexabut we're aware of the issue19:51:48
@emilazy:matrix.orgemilyyeah19:54:13
@emilazy:matrix.orgemily another option for Hydra is just a custom build-dir, but I think shouldn't be necessary 19:54:26
@emilazy:matrix.orgemily(pls no workarounds in Nixpkgs, it affects like a billion packages)19:54:46
@sternenseemann:systemli.orgsternithat's the last thing I want to spend my time with :p19:56:27
@arianvp:matrix.orgArianRedacted or Malformed Event20:22:25
23 Sep 2025
@sinan:sinanmohd.comsinan changed their profile picture.02:47:54
@a-kenji:matrix.orgkenji changed their display name from a-kenji to kenji.10:40:25
@nicof2000:matrix.org@nicof2000:matrix.org left the room.17:04:14
24 Sep 2025
@wolfgangwalther:matrix.org@wolfgangwalther:matrix.org With https://discourse.nixos.org/t/establishing-the-nixpkgs-core-team/69743 in mind, I need consultation: What are our options for a nixpkgs-core@nixos.org email address as a contact point? I heard that freescout is a thing and I assume we'll need to open a PR towards https://github.com/NixOS/infra/blob/main/non-critical-infra/modules/mailserver/mailing-lists.nix. How does this relate to freescout? Do we all need to be added as forwarders / is the account login there for freescout? Or is that a different thing? 18:23:30
@hexa:lossy.networkhexaWe'd need to set up a mailbox with a password. This happens in the infra repo.18:25:28
@hexa:lossy.networkhexaFreescout is managed by infini.sil18:25:40
@hexa:lossy.networkhexa* Freescout is managed by infini.sil.18:25:42
@hexa:lossy.networkhexa* Freescout is currently exclusively managed by infini.sil.18:26:05
@wolfgangwalther:matrix.org@wolfgangwalther:matrix.orgSo that would be a second step to tie this together?18:26:13
@hexa:lossy.networkhexaYeah.18:26:20
@wolfgangwalther:matrix.org@wolfgangwalther:matrix.org And freescout would access the account through the loginAccount given in infra, I guess. 18:26:40
@hexa:lossy.networkhexaalso, I'd suggest keeping it simple and go for nixpkgs@nixos.org maybe18:26:51
@hexa:lossy.networkhexa* also, I'd suggest keeping it simple and go for nixpkgs@nixos.org instead18:27:08

Show newer messages


Back to Room ListRoom Version: 6