| 13 Mar 2026 |
 raitobezarius (DECT: 7248) | winter would probably give a more direct referral ig | 15:35:10 |
 Winter | We are always strapped for people so the chances aren’t low!
IIRC you already applied in the past, right? (Let’s maybe move to DMs.)
| 15:36:56 |
| Winter | and ideally not on Matrix (you know how to reach me) bc i hate this platform too much | 15:38:57 |
 @rosssmyth:matrix.org | antithesis looks really cool but I do not want to move to VA | 18:46:07 |
| @rosssmyth:matrix.org | or sf | 18:46:54 |
| raitobezarius (DECT: 7248) | Ah true they have a strong in person policy | 19:17:13 |
| raitobezarius (DECT: 7248) | I forgot that | 19:17:15 |
| 15 Mar 2026 |
|  isabel changed their profile picture. | 20:54:47 |
| isabel changed their profile picture. | 20:55:03 |
 Lisanna | Tomorrow I think I will go through my merged nix PRs and port any applicable ones to Lix. Nothing too extravagant, just minor things. There are a few unmerged ones that are a bit more interesting, but I'll hold off on them for now in case they end up changing from review feedback. Later this week I'll probably join a Nix team meeting and bug them for reviews. | 23:11:13 |
| Lisanna | but feel free to comment on the unmerged ones in case there's anything applicable before I get them accepted and port them to Lix | 23:15:57 |
| 16 Mar 2026 |
|  draupnirchanged room power levels. | 10:16:20 |
| draupnirchanged room power levels. | 10:16:31 |
| Lisanna | Getting used to gerrit again, I'm working on porting https://github.com/NixOS/nix/pull/15105. That PR has two commits, one for the build hook signals and one for the progress bar shutdown message. Should I open these as different changes? | 13:31:30 |
| raitobezarius (DECT: 7248) | Yes, but be aware that Lix codebase is quite different in some areas (notably interruptions wise) from cppNix | 13:56:30 |
| 17 Mar 2026 |
|  zoë (she/her) joined the room. | 00:10:50 |
| zoë (she/her) | this is probably very dumb but: I'm trying to follow "Getting Started with Gerrit", and since it specifically points out "Now you can just git commit your change. No need to create a separate branch", i committed on main directly, but then the no-commit-on-branch commit hook failed because i tried to commit to main, so... am i missing something? | 03:11:46 |
| Lisanna | It's still probably a good idea to separate your changes into their own branches, otherwise you'll have to rebase just to edit changes that happened before you make another, unrelated change | 03:16:34 |
| zoë (she/her) | right, that makes sense, i was just a little confused at the docs ^^; | 03:17:23 |
| zoë (she/her) | aaaand first CL submitted :D
...it's an 8-bytes diff x) | 03:24:38 |
| Lisanna | * | 03:58:07 |
 piegames | In reply to @blokyk:matrix.org
this is probably very dumb but: I'm trying to follow "Getting Started with Gerrit", and since it specifically points out "Now you can just git commit your change. No need to create a separate branch", i committed on main directly, but then the no-commit-on-branch commit hook failed because i tried to commit to main, so... am i missing something? I think that sentence was about remote branches, but you're right it's confusing | 09:14:57 |
| 18 Mar 2026 |
| zoë (she/her) | hi, i recently got a review on one of my CLs (by eldritch horrors / pennae but they're not in this room ;-;), about using std::next to traverse a nix::Generator<T>, but i'm not very good with c++ so i'm not sure how to do that, since it seems that nix::Generator<T>.next returns a custom iterator implementation that differs from c++'s | 12:20:03 |
| zoë (she/her) | * hi, i recently got a review on one of my CLs (by eldritch horrors / pennae but they're not in this room ;-;), about using std::next to traverse a nix::Generator<T>, but i'm not very good with c++ so i'm not sure how to do that, since it seems that nix::Generator<T>.next returns a custom iterator implementation that differs from c++'s
(specifically, writing either std::next(gen.next()) or std::next(gen) gets me Candidate template ignored: substitution failure [with _InputIterator = iterator]: argument may not have 'void' type) | 12:21:50 |
| zoë (she/her) | * c++ noob time: hi, i recently got a review on one of my CLs (by eldritch horrors / pennae but they're not in this room ;-;), about using std::next to traverse a nix::Generator<T>, but i'm not very good with c++ so i'm not sure how to do that, since it seems that nix::Generator<T>.next returns a custom iterator implementation that differs from c++'s
(specifically, writing either std::next(gen.next()) or std::next(gen) gets me Candidate template ignored: substitution failure [with _InputIterator = iterator]: argument may not have 'void' type) | 12:27:21 |
 Qyriad | That comment is non-blocking (it's marked as "Resolved"), so it's not a huge issue if you can't figure that out | 12:27:19 |
| Qyriad | But the comment does also specify that it would have to be something like std::next(traces.begin(), requestTraceIdx) | 12:28:03 |
| zoë (she/her) | yeah i saw but i figured i'd like to do it anyways, since that loop is quite weird to me | 12:28:10 |
| zoë (she/her) | yeah yeah i also tried that (the second arg is optional and defaults to 1), i simplified it for the comment but i'll edit it | 12:28:55 |
| zoë (she/her) | * c++ noob time: hi, i recently got a review on one of my CLs (by eldritch horrors / pennae but they're not in this room ;-;), about using std::next to traverse a nix::Generator<T>, but i'm not very good with c++ so i'm not sure how to do that, since it seems that nix::Generator<T>.next returns a custom iterator implementation that differs from c++'s
(specifically, writing either std::next(gen.next(), idx) or std::next(gen, idx) gets me Candidate template ignored: substitution failure [with _InputIterator = iterator]: argument may not have 'void' type) | 12:29:05 |
