[Kde-pim] Possible bug in Akonadi::ChangeRecorder::replayNext()

[David Jarvie]

A ChangeReplay job seems to be getting stuck when the KAlarmResource starts up. Looking at the code in ChangeRecorder::replayNext(), it doesn't seem to handle the case highlighted below:

if ( !d->pendingNotifications.isEmpty() ) {
  ...
  if ( d->ensureDataAvailable( msg ) )
    ...
  else if ( !d->translateAndCompress( d->pipeline, msg ) ) {
    ...
  }
  ///// *THIS CASE ISN'T HANDLED*
} else {
  // This is necessary when none of the notifications were accepted / processed above ...
}

Shouldn't something happen in the unhandled case as well? KAlarmResource reaches that point and then seems to get stuck.

-- 
David Jarvie.
KDE developer.
KAlarm author -- http://www.astrojar.org.uk/kalarm
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kde-pim/attachments/20111116/562cbba9/attachment.sig>
-------------- next part --------------
_______________________________________________
KDE PIM mailing list kde-pim at kde.org
https://mail.kde.org/mailman/listinfo/kde-pim
KDE PIM home page at http://pim.kde.org/