!VRULIdgoKmKPzJZzjj:nixos.org

Nix Hackers

899 Members
For people hacking on the Nix package manager itself188 Servers

Load older messages


SenderMessageTime
16 Mar 2025
@jade_:matrix.orgjade_i currently do not have the brain space to fully think out how the dyndrv ideas work, but i will say that, as puck mentioned in lix dev a while ago, it could be the case in the future that we allow for input addressed drvs with different drv hashes to resolve to the same output hash for stuff like provenance metadata and other use cases like that where it does not affect the build itself, in the same way as fods currently allow. so having to generate the drvs from inside a dyndrv could be a trouble for the extension of the drv format?01:48:45
@roberthensing:matrix.orgroberthyou're considering this? https://github.com/NixOS/nix/issues/10780 10:29:28
@roberthensing:matrix.orgroberthit's already the case that drv hashes aren't 1:1 with input addressed output hashes, due to modulo hashing and FODs that occur in the derivation closure10:29:37
@puck:puck.moepuckbasically, yeah. i think .drv files (and, to some degree, their format) are distinct from "derivations" in a way that makes sense to rethink what they are and look like, because .drv files' hashes aren't stable to begin with10:31:42
@roberthensing:matrix.orgroberthI don't think generating drvs inside there has to be a problem, as presumably you could canonicalize them on the nix side?10:31:44
@roberthensing:matrix.orgroberthyeah, the issue tries to be more incremental in terms of change, but yeah, we basically could have a pipeline like exprs -eval-> instantiations of any suitable format -canonicalize-> derivations -build-> outputs10:34:34
@roberthensing:matrix.orgroberthor variations of that10:35:04
@0xcaff:matrix.orgMartin Charles joined the room.17:58:53
@Ericson2314:matrix.orgJohn Ericson hexa: We would like to no more about the bug that caused the builders to go to Lix 18:59:34
@Ericson2314:matrix.orgJohn Ericsonthat earlier github thread went of the rails, but the original idea of having some more information written down still stands19:00:02
@Ericson2314:matrix.orgJohn Ericson Thanks to infinisil (!) I got a link that works on the element electron app to the prior conversation in infra #infra:nixos.org, the link is: https://matrix.to/#/!RROtHmAaQIkiJzJZZE:nixos.org/$G9MBOn9CfSLkLiPqMhoN7KMnBEl6R4uRkLbFBm_KWBs?via=nixos.org&via=matrix.org&via=nixos.dev 19:37:51
@Ericson2314:matrix.orgJohn Ericsonrereading that, it does look like that no one really knows what the bug is, and other coredumps that e.g. might come from tests suites doing SIGABORT mean we do not have a good paper trail to figure out retroactively19:39:02
@Ericson2314:matrix.orgJohn EricsonDo you agree with that?19:39:06
@hexa:lossy.networkhexaI can roll back to nix in a few days20:25:01
@hexa:lossy.networkhexaI'm currently running with a workaround for nix not cleaning up build dirs in /tmp20:25:26
@hexa:lossy.networkhexathat got fixed in lix recently by pennae20:25:32
@hexa:lossy.networkhexacrucial since we build in a tmpfs20:25:40
17 Mar 2025
@jade_:matrix.orgjade_

yeah, and currently debugging protocol bugs is absolutely maddening. lix nightly currently has a known protocol bug due to concurrency and nar transfers and remote builders and gestures the whole protocol being extremely easy to screw up.

this is the idea we had for improving the experience of debugging protocol misbehaviour; implementation has not yet started: https://git.lix.systems/lix-project/lix/issues/734

00:12:20
@jade_:matrix.orgjade_ *

yeah, and currently debugging protocol bugs is absolutely maddening. lix nightly currently has a known protocol bug due to concurrency and nar transfers and remote builders and gestures the whole protocol being extremely easy to screw up and it is sorta reproducible (unusual for a protocol bug!).

this is the idea we had for improving the experience of debugging protocol misbehaviour; implementation has not yet started: https://git.lix.systems/lix-project/lix/issues/734

00:12:58
@jade_:matrix.orgjade_(we do not know of other protocol bugs in lix, fwiw)00:14:58
@jade_:matrix.orgjade_https://gerrit.lix.systems/c/lix/+/2639 here's the CL that fixed it IIRC, but i think there might be a second somewhere00:16:46
@jade_:matrix.orgjade_https://gerrit.lix.systems/c/lix/+/2666 ah it would be this00:17:08
@Ericson2314:matrix.orgJohn Ericson hexa: (or jade_) can you point me to the tmp cleaning commit? 00:17:28
@jade_:matrix.orgjade_see above00:17:33
@Ericson2314:matrix.orgJohn EricsonOK00:17:37
@Ericson2314:matrix.orgJohn Ericson I am ripping out building from scheduling finally right now 00:17:50
@jade_:matrix.orgjade_https://git.lix.systems/lix-project/lix/issues/678 issue here with discussion00:17:52
@Ericson2314:matrix.orgJohn Ericsonit is very satisifying00:17:56
@hexa:lossy.networkhexaand here https://github.com/NixOS/nix/issues/520700:18:08
@Ericson2314:matrix.orgJohn Ericson I made a OOP inheritence rats nest to wind up the balista, and then twang 00:18:27

Show newer messages


Back to Room ListRoom Version: 6