Not sure off the top of my head, but you can add multiple verbose flags (up to 5 iirc) for more verbosity (easiest as -vv and so on). Maybe one of those will clarify what it’s doing when it breaks.
Thanks @abathur ! I tried running with maximum verbosity (full log posted here), but oddly I’m only left with more questions!
The last few lines look relatively innocuous to my untrained eye:
building of '/nix/store/hyqg2r0xmxvz8xrnhxgcgwy57zn9zk8f-nix-shell-env.drv!*' from .drv file: loading derivation
acquiring write lock on '/nix/var/nix/temproots/96032'
downgrading to read lock on '/nix/var/nix/temproots/96032'
building of '/nix/store/hyqg2r0xmxvz8xrnhxgcgwy57zn9zk8f-nix-shell-env.drv!*' from .drv file: have derivation
substitution of 'sha256:60dac55dd52f83679561b3d6b57dc7741682e8e0b75e66e48e5cf1786e78f327!out': created
substitution of 'sha256:60dac55dd52f83679561b3d6b57dc7741682e8e0b75e66e48e5cf1786e78f327!out': woken up
substitution of 'sha256:60dac55dd52f83679561b3d6b57dc7741682e8e0b75e66e48e5cf1786e78f327!out': init
closing daemon connection because of an exception
error: unexpected end-of-file
This kind of errors is usually caused by a broken store path or tarball cache.
Please clear your nix related caches of involved users ($HOME/.cache/nix) and also run a store-check (sudo nix-store --verify --check-contents --repair).
The nix-store repair did find some broken entries in the store, which I find to be very odd, but repairing them and removing the cache has not had any impact on nix develop’s behavior