| 10 Mar 2025 |
| deprecated, moved to @poz:poz.pet changed their display name from jacek to deprecated, moved to @poz:poz.pet. | 00:30:33 |
| sinan changed their profile picture. | 02:45:54 |
| @marie:marie.cologne joined the room. | 11:35:30 |
| 11 Mar 2025 |
fzakaria | Redacted or Malformed Event | 01:53:56 |
fzakaria | Redacted or Malformed Event | 01:56:21 |
| sinan changed their profile picture. | 18:25:29 |
| sinan changed their profile picture. | 18:46:53 |
| 12 Mar 2025 |
fzakaria | If i use a separate store; how can i make it easily so my nix commands use it without doing --store | 01:57:34 |
puffnfresh | In reply to @fzakaria:one.ems.host If i use a separate store; how can i make it easily so my nix commands use it without doing --store can be set at compile time, or in nix.conf | 02:15:21 |
fzakaria | i was thining like a bind mount or somethig with nix-shell | 02:15:40 |
fzakaria | so it's temporary | 02:15:43 |
fzakaria | bind mounts doesn't work actually because i lose out on all my current tools in the current process | 02:24:13 |
fzakaria | in NixOS | 02:24:15 |
fzakaria | Okay this works though
nix run nixpkgs#fish --store /tmp/dyn-drvs
| 02:25:22 |
fzakaria | (not sure why unshare -> mount --bind doesn't though ) | 02:25:31 |
puffnfresh | didn't you say that you wanted to do it without using --store? | 03:44:11 |
fzakaria | i meant subsequent commands | 04:09:50 |
fzakaria | don't need the --store after that | 04:09:56 |
John Ericson | @roberthensing:matrix.org: FYI I noticed Linus Heckmann did some interesting recent commits to lix for GC fixes | 22:56:05 |
| 13 Mar 2025 |
Las | In reply to @fzakaria:one.ems.host If i use a separate store; how can i make it easily so my nix commands use it without doing --store NIX_CONFIG | 01:01:34 |
| @0rzklv:matrix.org joined the room. | 07:46:39 |
Sergei Zimmerman (xokdvium) | Fixing very significant debugger performance regression introduced in 2.21: https://github.com/NixOS/nix/pull/12645 | 13:42:40 |
Robert Hensing (roberth) | What do we think of suffixing fields with _ to make them visually distinct from locals/params? I'm open to it (implicit this-> may have been a mistake, hurting understanding and refactoring) but esp John Ericson tomberek Eelco Mic92 will also have to look at such code | 14:59:57 |
Mic92 | Robert Hensing (roberth): my lsp does it locally for my editor, but we don't have in github, so might be worth it. There is clang-tidy also can do this automatically: https://clang.llvm.org/extra/clang-tidy/checks/readability/identifier-naming.html#cmdoption-arg-ClassMemberPrefix | 15:05:03 |
Mic92 | * Robert Hensing (roberth): my lsp does it locally for my editor with colors, but we don't have in github, so might be worth it. There is clang-tidy also can do this automatically: https://clang.llvm.org/extra/clang-tidy/checks/readability/identifier-naming.html#cmdoption-arg-ClassMemberPrefix | 15:06:44 |
Robert Hensing (roberth) | Also suffix, nice! @Mic92 on GitHub we don't have that highlighting, for doing reviews | 15:19:39 |
niksnut | I wouldn't love it, seems a bit ugly. Yeah seems better if the lsp can figure it out. | 15:30:18 |
John Ericson | In reply to @roberthensing:matrix.org What do we think of suffixing fields with _ to make them visually distinct from locals/params? I'm open to it (implicit this-> may have been a mistake, hurting understanding and refactoring) but esp John Ericson tomberek Eelco Mic92 will also have to look at such code We do use a _ suffix for other things right now FYI | 15:40:41 |
niksnut | yeah, mostly for Sync state values | 16:00:58 |
Martin Schwaighofer | I'm trying to re-implement the way content-addressed derivations do dependency resolution from unresolved to resolved (aka basic) derivation, but outside of Nix - because I'm trying to do stricter validation with different signatures. I've gotten fairly far with that, but I'm seeing some "placeholder paths" like "/163l1qfs4mlpsl1g8m4ra6n08n8cscdgs9xgcbpijp61c1fjhcal" or "/0k24dfvijqra5pjhd1xhkg467fvh33cllgsxvpyklyhzymrm13xb/bin/bash" in the output of nix derivation show in places like the builder field of unresolved derivations. I don't know how I can resolve those myself, because I don't know how to find out either the unresolved derivation output it is associated with, or the store path nix wants it resolved to. In contrast, I can already resolve the outputs listed in inputDrvs to store paths myself just fine with the same results as Nix.
So I'm wondering, how do those placeholder paths work?
I saw that builtins.placeholder exists, but I don't really get how that relates to my problem from just reading the docs. 😅
(I also see one such path in resolved derivations, but there it's always the same "/1rz4g4znpzjwh1xymhjpm42vipw92pr73vdgl6xs1hycac8kf2n9" path in the "out" environment variable, so I think that's a different issue.)
| 16:06:18 |