Hi<br><br>Currently the initial indexing timing is buggy. The timer isn't paused when the indexing is paused. This patch fixes the issue.<br><br>I've done a minor amount of refactoring by adding two private slots - pauseIndexing and resumeIndexing. Should I have prefixed them with slot? I've refactored the code cause it makes it easier to read, and the TODO given (Add actions to the initial indexing notification) is now easily doable.<br>
<br>Now to the part I suck at - Testing. How in the world am I supposed to test it? It tried to change the location of the virtuoso repository (nepomukserverrc file) to a pen drive which didn't have adequate space, but that didn't really work. I started getting errors like - <br>
<div style="margin-left: 40px;">[/home/vishesh/kde/bin/nepomukservicestub] "/home/vishesh/kde/bin/nepomukservicestub(5372)" Error in thread 3052354416 : "SQLExecDirect failed on query 'sparql ask where { { <nepomuk:/ctx/7d689871-f944-460b-b0bf-75dbd444766c> ?p1 ?o1 . } UNION { ?s2 <nepomuk:/ctx/7d689871-f944-460b-b0bf-75dbd444766c> ?o2 . } UNION { ?s3 ?p3 <nepomuk:/ctx/7d689871-f944-460b-b0bf-75dbd444766c> . } UNION { graph <nepomuk:/ctx/7d689871-f944-460b-b0bf-75dbd444766c> { ?s4 ?4 ?o4 . } . } }' (iODBC Error: [OpenLink][Virtuoso iODBC Driver][Virtuoso Server]SR174: Log out of disk : while writing new IRI_ID allocation to log file)"<br>
</div><br>And I didn't get any notification saying there wasn't adequate space. :-/<br><br>Could somebody test it out by draining their laptop battery? I have no idea how I can emulate a battery on my desktop. <br>
<br>Thanks<br><br>- Vishesh Handa<br><br>