| 29 Apr 2026 |
 zoë (@blokyk) | actually Qyriad i removed this line that you added in f9d08cc44c, and i do get correct sources in lldb and gdb; is there some nuance i'm missing there? | 15:12:57 |
| zoë (@blokyk) | * actually Qyriad i removed this line that you added in f9d08cc44c, and i do get correct sources in lldb and gdb without needing any setup in the debugger (eg source-map in lldb); is there some nuance i'm missing there? | 15:13:45 |
| zoë (@blokyk) | * actually Qyriad i removed this line that you added in f9d08cc44c, and i do get correct sources in lldb and gdb without needing any setup in the debugger (eg source-map in lldb); is there some nuance i'm missing there? | 15:13:52 |
| 30 Apr 2026 |
|  @deezrightwinger:matrix.org joined the room. | 01:21:10 |
| @deezrightwinger:matrix.org | Redacted or Malformed Event | 01:21:24 |
 electria | I didn't know Lix had a Terms of Service (TOS), considering it's not a service...
A development chat is also most certainly not the right place for this
| 01:27:31 |
|  @hxr404:tchncs.de left the room. | 13:43:59 |
 Qyriad | In reply to @blokyk:matrix.org
actually Qyriad i removed this line that you added in f9d08cc44c, and i do get correct sources in lldb and gdb without needing any setup in the debugger (eg source-map in lldb); is there some nuance i'm missing there? Probably not. Iwrc there have been changes to Nixpkgs' default path mapping stuff since that commit, but if removing it now fixes things then yeet it! | 13:51:50 |
|  piegames banned @deezrightwinger:matrix.org (spam). | 18:33:21 |
|  isabel changed their profile picture. | 18:47:20 |
| 1 May 2026 |
 aloisw | Oh cool, I missed that when it came out: https://lwn.net/Articles/1054225/ | 11:19:40 |
| aloisw | It only took them almost seven years! | 11:19:49 |
 Sergei Zimmerman (xokdvium) | I thought it was an unmerged patchset? | 11:24:35 |
| aloisw | Not sure if it's the exact same API, but this looks like the entry point to the thing: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/tree/io_uring/register.c?h=v7.0.3#n1014 | 11:26:15 |
| Sergei Zimmerman (xokdvium) | Oh great | 11:32:28 |
| 16 May 2024 |
|  zrsk joined the room. | 13:54:49 |
 samrose | In reply to @lunaphied:lunaphied.me
I think there were a few CLs on the Gerrit but nothing being actively worked The other thing that I could do if it helps is test things and try to find bugs. I did do some C++ work in the past, but may lack the time to do it justice here at least for about 30 days or so | 15:55:29 |
| Qyriad | we are not in any rush 🙂 | 17:20:53 |
| samrose | Would it help to also test out the existing Lix code and try to find issues/bugs etc? | 17:23:21 |
| Qyriad | absolutely | 17:23:41 |
| samrose |
- how do people feel about the existing test suite that comes along with nix source code or Lix?
| 17:23:48 |
| Qyriad | it's pitiful | 17:24:10 |
| samrose | heh | 17:24:16 |
 raitobezarius | expanding it is cool | 17:24:23 |
| raitobezarius | writing new tests for builtins which are not tested | 17:24:30 |
| raitobezarius | new test behaviors, etc. | 17:24:32 |
| Qyriad | we have three flavors of test:
gtest (offer only available in libexpr and libutil) bash script virtual machine
the vast, vast majority of testing is in the "bash script" flavor and it is a mess | 17:25:01 |
| samrose | I was just going to ask on the "functional" tests: do we still like using bash there? | 17:25:56 |
| samrose | the last time that I worked on a major nix related cli project that used bash, or bats for testing, over time it became rather kind of hard to maintain | 17:26:42 |
| samrose | I am not usually a big python fan, but in that project we heard from some in the Rust community that they actually use Python to test CLI and seem to have success there. | 17:27:59 |
