Application start delayed until all locations are indexed.

[RayJW]

trafficstars

Describe the bug

Spacedrive doesn't launch until all locations that have been added are indexed. While this may seem desirable behaviour at first, I have a (probably common) use case where this causes huge issues. I added a location on an HDD because I want a convenient bookmark to get there and use the associated features. However, this location is a few hundred GB's big. This means whenever I try to launch Spacedrive after a few changes there the application doesn't launch for tens of seconds if not minutes. Luckily, I know the app is not broken because I can physically hear the indexing on the HDD, but I think that's not a very convenient way of handling things. Personally, I think it would make much more sense to have a disclaimer or banner when navigating to such a location that indexing is not done yet, instead of making the file manager inaccessible for potentially multiple minutes.

Reproduction

1. Add any big location to Spacedrive and let it probably be on an HDD or a very large folder on a slow SSD.
2. Make many changes to this folder, let's say you add a location where you store games and install a new game.
3. Start Spacedrive and look at the delay while starting and also monitor disk activity.

Expected behavior

Spacedrive should just start and continue indexing in the background. Probably also add a warning or disclaimer to features that rely on the indexing to make the user aware of unexpected behaviour when e.g. searching.

Platform and versions

I'm using the 0.2.4 deb alpha installed on Pop!_OS 22.04 which is based upon Ubuntu 22.04 with the following output for pnpm --version && cargo --version && rustc --version:

8.15.4
cargo 1.76.0 (c84b36747 2024-01-18)
rustc 1.76.0 (07dca489a 2024-02-04)

Stack trace

No response

Additional context

No response

[HeavenVolkoff]

This will be resolved by the new job system #2476

[RayJW]

Sorry for pinging you @HeavenVolkoff but before recreating an old issue, I'm not sure if I'm doing anything wrong, but Spacedrive still took over 4 minutes to launch on version 0.4.0 with the same disk setup. Do I have to manually enable the new job system, or is there anything else I missed?

[HeavenVolkoff]

Hun... this is weird. @RayJW could you upload a recent log file (~/.local/share/spacedrive/logs)? So I can see if there is something going wrong with the indexer

[RayJW]

Sure, thanks for helping out! sd.log.2024-07-23.log is the most recent log, looks like it's been about a month and a half since I started Spacedrive the last time according to the log files. So, there certainly were a lot of changes that probably had to be indexed.