19 May 2025 |
| oak 🏳️🌈♥️ changed their display name from oak to oak 🏳️🌈♥️. | 11:00:36 |
| mgaughan joined the room. | 20:36:06 |
20 May 2025 |
@trofi:matrix.org | You can make linux select() to work for large FDs as well, but you would have to roll your own bit setting code to avoid glibc's limit (or override FD_SETSIZE ). | 05:41:45 |
21 May 2025 |
fzakaria | cherry-pick: https://github.com/NixOS/nix/pull/13241 | 02:28:13 |
Winter | that should probably have --author set to the original author ^^ | 02:30:45 |
tomberek | I might be totally clueless, but I don't know why https://github.com/NixOS/nixpkgs/pull/408846 fails on aarch64-linux. Anyone can help? | 03:24:12 |
@trofi:matrix.org | /build/source/build/src/nix/nix-store: cannot execute: required file not found suggests the binary is corrupted perhaps? | 06:00:09 |
| WeetHet changed their profile picture. | 10:59:01 |
| sinan changed their profile picture. | 11:59:58 |
| sinan changed their profile picture. | 12:00:45 |
emily | is there a way to trace imports of an evaluation that isn't as horribly slow as nix eval -v -v or scopedImport { import = x: builtins.trace x (import x); } ? | 13:26:03 |
emily | actually I guess the latter needs to be recursive which would make it even slower | 13:27:14 |
Sergei Zimmerman (xokdvium) | In reply to @emilazy:matrix.org is there a way to trace imports of an evaluation that isn't as horribly slow as nix eval -v -v or scopedImport { import = x: builtins.trace x (import x); } ? Hm, do you need the trace to be super precise? Would a flamegraph suffice? | 14:33:28 |
emily | yes, precision is the aim (dependency tracking) | 14:34:24 |
emily | though only a subset of paths (beneath a given root) are required | 14:34:39 |
emily | possibly I can use that to help short-circuit things | 14:35:04 |
hacker1024 | Is modifying the implementation of `import` in the Nix source itself an option? | 14:36:37 |
emily | I suppose I'd really rather not :) | 14:46:21 |
emily | I don't really know why -v -v is slow in the first place | 14:46:35 |