[FileIndexScheduler] Force evaluation of indexerState after suspend/resume

Authored by bruns on Feb 11 2020, 3:51 PM.



When the scheduler is idle when suspending scheduleIndexing() has to be
triggered, otherwise indexerState is only evaluated on the first external
trigger (e.g. a changed file).

On resume, scheduleIndexing() never updated the state, as Suspended did
not qualify as an Idle state. This had the effect of the scheduler being
stuck in the Suspended state.

Test Plan

balooctl suspend && balooctl status
balooctl resume && balooctl status

Diff Detail

R293 Baloo
Automatic diff as part of commit; lint not applicable.
Automatic diff as part of commit; unit tests not applicable.
bruns created this revision.Feb 11 2020, 3:51 PM
Restricted Application added a subscriber: kde-frameworks-devel. · View Herald TranscriptFeb 11 2020, 3:51 PM
bruns requested review of this revision.Feb 11 2020, 3:51 PM
ngraham accepted this revision.Feb 11 2020, 5:01 PM

Whoops. Can confirm the bug and the fix.

This revision is now accepted and ready to land.Feb 11 2020, 5:01 PM
This revision was automatically updated to reflect the committed changes.