amy null

https://github.com/Discord-Datamining/Discord-Datamining/commit/8ef81f4622ebf6f733a120a96992b9b7b7d009a7

To follow up on this, it doesn’t happen *every* day; today’s run went fine. It’s just concerning that it can happen at all and leave my index in a state...

@Kerollmops: - I previously ran 1.6.0 with ~550k documents, and upgraded to 1.7.6 ahead of the increased index size. I did rebuild my index entirely when moving to 1.7.6. -...

Hello 🌈 This has not occurred again since the first time it happened, so I'm unsure if it was "just" a transient issue. I'll be sure to update if it...

I have not been able to reproduce this thus far and will close this unless it comes up again (:

I ran into this today as well, using the `1.6.0-1` deb package on an Ubuntu server (no WSL or similar). Exact same error that @balach reported. Deleting the entire index...

I ran into this again yesterday (still on `1.6.0`) and got some more details that may help: - Documents are ingested in batches of 500~2500 at a time, ~540k total...

This issue stopped reproducing on v1.6.2 for me at some point; unfortunately I never managed to pinpoint the specific problematic document.

The most effective way of doing this without root seems to be tying squish to systemd, and using the user slice cgroups to create subcgroups.

Related to #4.