The 'stop' flag was not set when the scheduler is quit, and the content
indexer thread would keep running until it had processed all documents
marked in the DB.
Details
Details
- Reviewers
ngraham astippich poboiko - Group Reviewers
Baloo - Commits
- R293:d74d1cbb65db: [FileIndexScheduler] Stop the indexer when quit() is called via DBus
feed some files into the content indexer
try to stop the indexer, e.g. balooctl stop or using DBus
-> the content indexer should stop after the current batch
Diff Detail
Diff Detail
- Repository
- R293 Baloo
- Lint
Automatic diff as part of commit; lint not applicable. - Unit
Automatic diff as part of commit; unit tests not applicable.
Comment Actions
Yes, mostly - the "after the current batch" caveat applies, so there may be still some delay.