Benno Fünfstück

@rocallahan the stacktrace at after that message was printed is: ``` gdb-peda$ bt #0 0x00007f7ffc72fad0 in __accept_nocancel () from /usr/lib/libpthread.so.0 #1 0x0000000000461477 in rr::GdbConnection::await_debugger(rr::ScopedFd&) () #2 0x0000000000474bfe in ?? ()...

Alright, I think I've managed to reproduce the original problem: ``` (rr) x/10i $pc => 0x55dd0eb56f30 : mov -0x30(%rbp),%rax (rr) reverse-stepi Program received signal SIGINT, Interrupt. core::ptr::{{impl}}::offset (self=0x7f0b28636c40 "\azA\016\375\326y\200\346s\000", count=0)...

I don't have the trace anymore, and don't remember the details for this issue. Feel free to close

This patch causes the following panic for discourse_distrust (a go app I am using in my deployment): ``` symlink error, trying /nix/store/wqn056sx2amxf3qx2x5j695x6ggxb3wb-go_v1.1.4/codec symlink /nix/store/wqn056sx2amxf3qx2x5j695x6ggxb3wb-> symlink error, trying /nix/store/wqn056sx2amxf3qx2x5j695x6ggxb3wb-go_v1.1.4/codec/0_importpath.go symlink /nix/store/wqn056sx2amxf3qx2>...

This feels to me like it is adding another quirk to python packaging. If we do this, `setup.py` will depend on `Pipfile.lock` which is *very* weird: now abstract dependencies in...

Ah, arm64 linux runners appear to in private beta for github ci :( https://github.com/orgs/community/discussions/19197 So it is not possible to build this with Github CI right now, except using qemu...

I have no strong opinion on this, if you think it makes sense, we can do this.

Perhaps this could also be restricted to the beginning of the file, not sure about that though.

Yes, that's also a possibility. My argument against that approach is this: * Removing the unused arguments IMO does not improve readability at all * Keeping them is more economic...

Yes feel free to