| 13 Oct 2025 |
 mrdev023 | Hi everyone, i want to know what's the recommendation to work on nixpkgs. Currently, i tried to open nixpkgs project on vscode and neovim. But it's very slow because nixpkgs have a lot of folders.
Maybe open only the correct directory ? | 17:12:11 |
 K900 | Wrong room | 17:16:05 |
| K900 | You want #Nixpkgs / NixOS contributions | 17:16:14 |
| mrdev023 | thx | 17:16:40 |
| mrdev023 | I can't join it K900 .... | 17:17:15 |
| mrdev023 | My bad just a matrix bug | 17:17:44 |
|  @perpetrator1:matrix.org left the room. | 19:22:59 |
 John Ericson | Robert Hensing (roberth): does nix eval override the "always trace" thing? | 20:47:57 |
 roberth | John Ericson: The problem there is that printValue only prints the "final" line, which is quite sensible, considering that it may print many "values" that throw | 20:49:08 |
| John Ericson | Robert Hensing (roberth): this is implemented in the Printer class thing? | 20:50:38 |
| roberth | yeah | 20:50:50 |
| John Ericson | I would hope it could be more "semantic" and not just chop an error at one line? | 20:51:11 |
| roberth | for sure, it's the exception message without the traces | 20:51:57 |
| John Ericson | printError_ in this? | 20:52:13 |
| John Ericson | Robert Hensing (roberth): OK throwing in the towel on tracing :) | 21:01:00 |
| John Ericson | I left comments for the storing of the reason | 21:01:10 |
| John Ericson | it should be very easy | 21:01:12 |
| 14 Oct 2025 |
|  @douglasfunster:matrix.org joined the room. | 10:42:38 |
|  SigmaSquadron joined the room. | 12:46:23 |
 Mic92 | https://www.phoronix.com/news/Fedora-Nix-Dir-Approved | 21:08:35 |
| 15 Oct 2025 |
 fzakaria | oh | 00:28:16 |
| fzakaria | wow | 00:28:16 |
| fzakaria | is there a way to make this more comprehnsible why it happens
[1/0/1 copied (176.7/176.7 MiB), 29.1 MiB DL] fetching source from https://cache.nixos.org
| 00:30:23 |
| fzakaria | I would be down to work on that.. | 00:49:13 |
| Mic92 | What do you mean? | 06:25:52 |
| Mic92 | In reply to @justinrestivo:matrix.org
Hello! Any chance there's a spec about the different Fields provided for each ActivityType in the nix logger? Right now to answer this question I'm grepping the nix codebase for each ActivityType and looking at the arguments to the Activity::Activity constructor to infer the field types and number (if any exist). I'm wondering if there's an easier/more canonical way to do this. I don't think so. There is maybe nix-output-monitor. I think also https://github.com/Thymis-io/thymis had a parser somewhere | 06:32:47 |
 maralorn | justinrestivo: This might help. https://github.com/maralorn/nix-output-monitor/blob/main/lib/NOM/Parser/JSON.hs | 07:44:59 |
| maralorn | Though note that the nom parser trys to be the union of the codes that nix, lix and determinate nix emit. | 07:45:41 |
| fzakaria | Like can it say "Git cache is out of date" or "Tarball expires" or w/e is causing the fetching source. | 13:18:00 |
| fzakaria | * Like can it say "Git cache is out of date" or "Tarball expires" or w/e is causing the fetching source.
(I'm thinking it's a flake input fetch although it writes "source fetch") | 13:18:49 |
