lorri Crash Report

[bb010g]

Describe the bug
lorri just kinda crashed on me. Twice? lorri's service did not restart until the second recorded crash.

To Reproduce
Steps to reproduce the behavior:

1. Save a watched Nix file.
2. Unsure of what caused the first crash.
3. Unsure of what kicked off the second crash either (the one that actually led to a restart).

Expected behavior
lorri probably didn't want to crash? Also, lorri's service should have restarted after the first crash message.

Metadata
Two crash reports were generated, /tmp/report-e4ca6a0e-32e3-43af-8f08-4158725d26b4.toml and then /tmp/report-70d2e818-a6b2-4092-a39f-40b0bd199930.toml.

report-e4ca6a0e-32e3-43af-8f08-4158725d26b4.toml
report-70d2e818-a6b2-4092-a39f-40b0bd199930.toml

$ lorri info --shell-file shell.nix
lorri version: 1.2
GC roots exist, shell_gc_root: "/home/bb010g/.cache/lorri/gc_roots/77d840ebbe259d734e5d4b1be4f6f954/gc_root/shell_gc_root"

$ uname -a
Linux nixzed 5.9.16 #1-NixOS SMP Mon Dec 21 12:28:21 UTC 2020 x86_64 GNU/Linux

Additional context

$ journalctl --user -xef -u lorri.service # abridged
Feb 13 18:08:06 nixzed lorri[28150]: Feb 13 18:08:06.880 INFO build status, message: BuildEvent(Started { nix_file: NixFile("/home/bb010g/Documents/go/git-lfs/shell.nix"), reason: FilesChanged(["/home/bb010g/Documents/go/git-lfs/shell.nix"]) })
Feb 13 18:11:41 nixzed lorri[28150]: We have generated a report file at "/tmp/report-e4ca6a0e-32e3-43af-8f08-4158725d26b4.toml". Submit an issue or email with the subject of "lorri Crash Report" and include the report as an attachment.
Feb 13 18:14:23 nixzed lorri[28150]: We have generated a report file at "/tmp/report-70d2e818-a6b2-4092-a39f-40b0bd199930.toml". Submit an issue or email with the subject of "lorri Crash Report" and include the report as an attachment.
Feb 13 18:14:23 nixzed systemd[1823]: lorri.service: Main process exited, code=exited, status=101/n/a
Feb 13 18:14:23 nixzed systemd[1823]: lorri.service: Failed with result 'exit-code'.
Feb 13 18:14:23 nixzed systemd[1823]: lorri.service: Scheduled restart job, restart counter is at 1.

$ systemctl --user status lorri.service # abridged
● lorri.service - lorri build daemon
     Loaded: loaded (/nix/store/b67v92zyvddlpjf77s8v42b2mpdlm75w-home-manager-files/.config/systemd/user/lorri.service; linked; vendor preset: enabled)
     Active: active (running) since Thu 2021-02-11 20:57:58 PST; 1 day 21h ago
TriggeredBy: ● lorri.socket
   Main PID: 28150 (lorri)
     CGroup: /user.slice/user-1000.slice/user@1000.service/lorri.service
             └─28150 /nix/store/nn6vdy8172whwr5h1r6y6gwj3y54pgw0-lorri-1.2/bin/lorri daemon

Feb 13 18:08:06 nixzed lorri[28150]: Feb 13 18:08:06.880 INFO build status, message: BuildEvent(Started { nix_file: NixFile("/home/bb010g/Documents/go/git-lfs/shell.nix"), reason: FilesChanged(["/home/bb010g/Documents/go/git-lfs/shell.nix"]) })
Feb 13 18:11:41 nixzed lorri[28150]: We have generated a report file at "/tmp/report-e4ca6a0e-32e3-43af-8f08-4158725d26b4.toml". Submit an issue or email with the subject of "lorri Crash Report" and include the report as an attachment.
$ systemctl --user status lorri.service
● lorri.service - lorri build daemon
     Loaded: loaded (/nix/store/b67v92zyvddlpjf77s8v42b2mpdlm75w-home-manager-files/.config/systemd/user/lorri.service; linked; vendor preset: enabled)
     Active: active (running) since Sat 2021-02-13 18:14:23 PST; 8min ago
TriggeredBy: ● lorri.socket
   Main PID: 19086 (lorri)
     CGroup: /user.slice/user-1000.slice/user@1000.service/lorri.service
             └─19086 /nix/store/nn6vdy8172whwr5h1r6y6gwj3y54pgw0-lorri-1.2/bin/lorri daemon

Feb 13 18:14:23 nixzed systemd[1823]: Started lorri build daemon.
Feb 13 18:14:23 nixzed lorri[19086]: Feb 13 18:14:23.599 INFO ready

[mhuesch]

I have observed the same (modulo memory addresses) crash report as report-e4ca6a0e-32e3-43af-8f08-4158725d26b4.toml.txt.

vayu :: ~/Downloads » diff -d report-e4ca6a0e-32e3-43af-8f08-4158725d26b4.toml.txt /tmp/report-2a5e24aa-298b-4134-b217-8fe604cbfc5b.toml
15,19c15,19
<    0: 0x55d26d50b666 - std::sys_common::backtrace::__rust_begin_short_backtrace::hf8f4b2945b22d527
<    1: 0x55d26d5467a5 - core::ops::function::FnOnce::call_once{{vtable.shim}}::hecbb3ea2547f4ebf
<    2: 0x55d26d6facca - std::sys::unix::thread::Thread::new::thread_start::h2dd53bf76d714ab0
<    3: 0x7f873bf8bead - start_thread
<    4: 0x7f873bea2d2f - __GI___clone
---
>    0: 0x56071d0e4666 - std::sys_common::backtrace::__rust_begin_short_backtrace::hf8f4b2945b22d527
>    1: 0x56071d11f7a5 - core::ops::function::FnOnce::call_once{{vtable.shim}}::hecbb3ea2547f4ebf
>    2: 0x56071d2d3cca - std::sys::unix::thread::Thread::new::thread_start::h2dd53bf76d714ab0
>    3: 0x7fae4e3a8ead - start_thread
>    4: 0x7fae4e2bfd2f - __GI___clone

I also am unsure of what caused it - I don't recall doing anything out of the ordinary prior to the crash 🤔