| 3 Mar 2026 |
 hexa | maybe someone here can clarify the meaning of this screen 🤡 | 15:31:41 |
| hexa | because two of the m1 minis we sent to a hosting location show this | 15:32:08 |
| hexa | and boy does this look like mdm fuckery | 15:32:21 |
 Randy Eckenrode | That’s what it looks like to me. | 15:32:37 |
| hexa | so not properly unregistered from mdm, cool. | 15:32:54 |
| hexa | these are foundation owned fwiw, so this is super funny, but I'm not laughing. | 15:33:26 |
 antifuchs | so this is odd, man ln shows me the man page for nixpkgs ln (doesn't say, but I assume coreutils), but which -a ln only shows /bin/ln, which has a wildly diverging flag set from the manual page one | 15:53:22 |
| antifuchs | wait that's not true, it's just macOS documenting a flag that no longer exists apparently | 15:57:58 |
 samasaur | man -wa ln may be helpful? | 16:00:00 |
| antifuchs | oh, yep, that's the flag. it's the regular built-in manpage. I just got confused by which ln was used in the activation script (: | 16:01:53 |
| antifuchs | (that script uses the coreutils one, which stumbles over -h) | 16:02:35 |
 emily | seems like an empty rebrand to me | 18:22:00 |
| Randy Eckenrode | Probably, but dropping down to only six performance cores doesn’t seem very pro. | 18:55:49 |
 Sarah Clark | It sounds like they didn't improve the cooling enough so we get a pile of the slower cores | 19:26:57 |
| Sarah Clark | I have a M3 Max and set num-cores to not touch the efficiency cores most of the time. | 19:28:02 |
| Randy Eckenrode | I limit the number of simultaneous jobs because otherwise Nix happily schedule way too many simultaneous builds for a workstation. | 19:29:44 |
 WeetHet | By the way, did someone investigate the QoS classes in the end? | 21:09:12 |
|  PJ set a profile picture. | 23:49:02 |
| 4 Mar 2026 |
 Lun | https://github.com/NixOS/nixpkgs/pull/496445 | 02:09:13 |
| 5 Mar 2026 |
|  @logn:zirco.dev left the room. | 02:29:05 |
| emily | hexa: do you have any feeling for roughly when Darwin staging queue started being especially bad? I am wondering if it might be https://github.com/NixOS/nixpkgs/pull/442945 (because of the mistake mentioned in https://github.com/NixOS/nixpkgs/pull/490358), though that was a few months ago now | 15:04:22 |
| emily | I'm inclined to merge https://github.com/NixOS/nixpkgs/pull/490358 and see if it makes the next cycle less bad, but I probably won't notice one way or the other myself :) | 15:04:55 |
| hexa | no, sadly not | 15:05:45 |
| hexa | maybe vcunat remembers | 15:06:02 |
| hexa | I'd say for the last two months I had to reboot macs a few times because they ran full and had stuck jobs | 15:06:33 |
| emily | vcunat? :) | 15:07:00 |
| emily | it seems plausible that libc++ hardening could make Clang meaningfully slower or whatever | 15:07:10 |
| hexa | anyway, the backlog this time was around 55k packages when linux was finished | 15:07:36 |
| hexa | and the machines are doing like 10k per day? | 15:07:54 |
| hexa | I think we tend to say the current total capacity is like 30k jobs per day | 15:08:31 |
