No way to interrupt indexing run

[ArneBachmann]

CTRL+C doesn't get through. And when I stop via CTRL+Break (hard kill), the SQLite database transactions are not committed and therefore I cannot search anything (WAL file remains). I guess I would enjoy an interruptible and resumable index run.
E.g. using try: ... except: KeyboardInterrupt: ...

[dnlzrgz]

Yes! I'm sorry, and I'm fully aware of that issue. The thing is that files are indexed using multi-threading while posts are fetched concurrently, and then, at the end, the virtual FTS5 table is updated to allow for the search. This past weekend, I was looking for solutions to close the threads gracefully, but I didn't have time to finish the changes and publish a new version.

[ArneBachmann]

Oh no, don't be sorry for giving something out for free. I wrote a similar tool myself, but never got it finished, so I'm just curious in similar solutions. I could take a look, but my time is just very limited for these things.

[ArneBachmann]

It might be possible to .cancel() the individual index runs if you keep references to them, so that the CLI stops after the current directory. You could let the user know via a console output "[yellow]Stopping the index run..."

• https://superfastpython.com/threadpool-python/#Step_1_Create_the_Thread_Pool