jokorone
jokorone
I'm very sorry for the linting, clippy doing it's thing 🤷
I merged the dev branch into my branch and added a task_running flag to check if the old thread is still running. While it's still debatable if a 30sec interval...
it seems to me the current code is trying to call `.unwrap()` on a [poisened mutex](https://doc.rust-lang.org/std/sync/struct.Mutex.html#poisoning) when accessing state in the `run_cache_interval` loop. ``` loop { interval.tick().await; let mut guard...
I'll look into the other issue you mentioned in the OP.
@HenryRoutson at first I experienced the same, but deleting the `system_cache.json` and resolved the issue. From the [docs](https://doc.rust-lang.org/std/sync/struct.Mutex.html#poisoning): > [...] where a mutex is considered poisoned whenever a thread panics...
@FormalSnake how much diskspace are you using? 👀
> I've tested it, it works for me as well. I think the issue is that the code keeps triggering the recaching without checking if the previous caching routine is...