D21673: [FileIndexScheduler] Ensure indexer is not run in suspended state

Stefan BrĂ¼ns noreply at phabricator.kde.org
Sat Jun 8 18:06:08 BST 2019


bruns created this revision.
bruns added reviewers: Baloo, ngraham, astippich, poboiko.
Herald added projects: Frameworks, Baloo.
Herald added a subscriber: kde-frameworks-devel.
bruns requested review of this revision.

REVISION SUMMARY
  After commit b13453360685 <https://phabricator.kde.org/R293:b134533606857226afa067a814999790b868c3f1> ("Use flag to track when a runner is going idle")
  the scheduler may be triggered from the finished content indexer thread,
  picking up any remaining work and overwriting the "Suspended" state.
  
  Use a flag variable for the suspend state, and determine the current
  state in the scheduler loop, like it is done for e.g. the onBattery
  state.

TEST PLAN
  feed some files into the content indexer
  suspend using `balooctl suspend`, content indexer stops and stays stopped

REPOSITORY
  R293 Baloo

BRANCH
  scheduler

REVISION DETAIL
  https://phabricator.kde.org/D21673

AFFECTED FILES
  src/file/fileindexscheduler.cpp
  src/file/fileindexscheduler.h

To: bruns, #baloo, ngraham, astippich, poboiko
Cc: kde-frameworks-devel, LeGast00n, domson, ashaposhnikov, michaelh, astippich, spoorun, ngraham, bruns, abrahams
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kde-frameworks-devel/attachments/20190608/5775af35/attachment-0001.html>


More information about the Kde-frameworks-devel mailing list