!zghijEASpYQWYFzriI:nixos.org

Hydra

393 Members
113 Servers

Load older messages


SenderMessageTime
6 May 2026
@orzklv:floss.uzOrzklv joined the room.15:35:39
10 May 2026
@Ericson2314:matrix.orgJohn Ericson Mic92: I noticed cachix push is not working for hydra? 21:14:55
@Ericson2314:matrix.orgJohn Ericsonso the merge queue ends up rebulding the rust a second time21:15:07
11 May 2026
@joerg:thalheim.ioMic92 @Ericson2314:matrix.org: it needs secret access. It won't work for your fork 07:11:57
@joerg:thalheim.ioMic92* @Ericson2314:matrix.org: it needs secret access. It won't work for your fork. You would need to push the branch to the hydra repo07:12:45
@Ericson2314:matrix.orgJohn Ericson @joerg:thalheim.io that's for any PR from a forked repo? 13:51:12
@hexa:lossy.networkhexayes14:02:33
@hexa:lossy.networkhexaotherwise you'd open yourself up for cache pollution14:02:43
@joerg:thalheim.ioMic92What hexa says14:50:00
@joerg:thalheim.ioMic92We still have some caching in the other direction for pull requests 14:50:27
@Ericson2314:matrix.orgJohn EricsonOK14:54:44
@Ericson2314:matrix.orgJohn Ericsoncool14:54:46
@janne:hess.oooJanneHey, regarding the RFC process that we talked about 2 meetings back. Is this still coming or have there been no functional changes been thought of the last 4 weeks? Or maybe I missed something between the ~105 commits that were apparently not functional changes and rather fixes and tiny PRs?18:54:12
@Ericson2314:matrix.orgJohn EricsonRFC process?19:06:53
@Ericson2314:matrix.orgJohn Ericsonreview not nixos/rfcs?19:07:25
@janne:hess.oooJannein the hydra repo issues19:14:57
@Ericson2314:matrix.orgJohn Ericsonto be honest I forget which specific changes I was going to flag for review. In the most recent hydra meeting with Simon we went over some socket activation stuff and were mainly focused on the deployment issues19:19:30
@Ericson2314:matrix.orgJohn EricsonI had found a way to do a version of the CA / dyn drv stuf with no DB schema changes and that is good enough for now. the DB schema version can wait until it is actually deployed19:20:21
@Ericson2314:matrix.orgJohn Ericsonfor the best few days, I have been focusing on the feedback from hexa's deployment attempts trying to figure out what is causing that / make it impossible for builders to build dependendencies that should be built already19:21:03
@janne:hess.oooJannenot sure that even matters anymore btf19:22:54
@janne:hess.oooJanne* not sure that even matters anymore tbf19:22:56
@janne:hess.oooJanne* not sure that even matters anymore tbh19:23:02
@Ericson2314:matrix.orgJohn Ericson....because you think the code is all slop and never gonna work.....?19:24:37
@frooastside:wolkeneis.devFrooastside joined the room.19:28:10
@janne:hess.oooJanne

Yes but no. I don't doubt whether the code will work, it most likely will with a probability of failure compared to a human. The actual issue I have with the entire topic is not the LLM but the way it's handled and applied. There are multiple issues I see, all connected to maintainability.

  • There is currently a lot of work going on that seems unfocused to the actual goal of getting the new qr to prod and each of these changes introduces additional risks of bugs
  • Most of the code is self-merged with only one person (I hope) ever seeing that code and no additional person knowing any of the details without clicking through the 100 commits that have happened since the qr. Which is getting less reasonable with the current pace of new commits and PRs. Also, there is no actual rush for most of these changes. What matters right now is getting the qr to prod so we can have take a look at regressions and fix them after such a huge change
  • There have been surprising changes where I would have expected the entire team to be consulted like introducing a toml formatter that is in my perspective very subpar
  • We have very limited human resources in the project. Before me there was only graham (and someone else, sorry I forgot the name) and I don't see how permanent the current amount of people is. I think (don't pin me on this statement) I have been the longest maintainer of the software and I assume that after right now, it will be back to me again (if I decide this works for me) and the others following different projects (which is fair, there is no lifetime requirement) - leaving me with a codebase I have no idea how it works (like back when I started) in a state only a LLM can understand and which I am not willing to spend my own money on the amount of tokens it requires. Unfortunately, there has to be someone maintaing this software and both my past experience and what I think people I have worked with expect of me gets me into the situation where I will be doing the required work
19:53:04
@Ericson2314:matrix.orgJohn EricsonI would liek to work more closely but how often have you been checking matrix etc?19:56:09
@Ericson2314:matrix.orgJohn EricsonRight now I have a limitted time budget to get a lot of things done, including fixing preexisting issues19:56:26
@Ericson2314:matrix.orgJohn Ericsonwhich again is my focus right now, I tend to solve all problems with more refactoring19:56:54
@Ericson2314:matrix.orgJohn Ericson(we're pretty well done on the new feature work, actually)19:57:25
@Ericson2314:matrix.orgJohn Ericsonthere has been no unattended LLMs, I read code very quickly19:58:00

Show newer messages


Back to Room ListRoom Version: 6