Lix Development | 415 Members | |
| (Technical) development of Lix, the package manager, a Nix implementation. Please be mindful of ongoing technical conversations in this channel. | 139 Servers |
| Sender | Message | Time |
|---|---|---|
| 2 Aug 2025 | ||
| I am increasingly of the opinion that it is unwarranted complexity. we already print out a note naming the build directory on failure | 15:50:36 | |
| it is just easy to miss and doesn't identify the failing derivation | 15:50:45 | |
| IMO making it attached to the error of the derivation failing (and therefore more prominent) would solve the UX case with fewer moving parts | 15:51:09 | |
| right now you get e.g.
| 15:51:50 | |
| we should simply list the retained build directory in the "For full logs" portion of the message | 15:52:00 | |
| | 15:52:02 | |
In reply to @emilazy:matrix.orgyeah you're right | 15:52:14 | |
| i think this is a much better idea | 15:52:17 | |
(I didn't notice the note: for a long while previously before trying to test this because it doesn't even have any colour or anything) | 15:52:40 | |
| btw it would also be really nice if the log command was on its own line (and so the build directory too I guess), so you could more easily select the whole line and paste it | 15:53:37 | |
| I spend too much of my life dragging the mouse over only the right portion of the message | 15:53:57 | |
| something like
| 15:55:15 | |
| (or maybe even "To inspect the build directory: … cd /nix/var/nix/b/…") | 15:55:31 | |
| do you mind me pushing fixes to your chain? | 15:55:42 | |
| the compile stuff i mean | 15:56:09 | |
| IIRC I have unpushed WIP amendments already, so workflow-wise it's probably easier for me if you just leave suggestions (but if you want to get the CI results feel free). the +2s would need repeating after I push out my own fixes anyway I think | 15:57:24 | |
| don't worry | 15:57:35 | |
| this was just in case this would do you a favor | 15:57:40 | |
| there was some integration test issue with temporary stuff in a build dir and I need to check whether it's a test problem or a code problem | 15:58:20 | |
| (+2 will repeat but much easier to review the diff between patchset N -1 and patchset N) | 15:58:27 | |
| I'm currently in the middle of testing Rust stuff re: reproducibility | 15:58:32 | |
| will let the chef cook | 15:58:44 | |
| maybe i will tack the error message UX improvements | 15:58:52 | |
| or would you prefer to take care of it yourself? | 15:58:58 | |
| fwiw | 16:00:28 | |
| on my side | 16:00:29 | |
for --keep-failed? feel free, that could even land separately I think | 16:00:59 | |
| since the code paths should not interfere | 16:01:06 | |
| for reference for those who are interested in testing the HEAD:
should be sufficient on the top of the chain | 16:01:46 | |
| (last hunk is a casualty of last-minute manual reformatting…) | 16:06:23 | |