As the % operator has higher precedence than the + operator this change correctly fixes the string formatting resulting the desired "DELETED/$FOLDERHIERARCHY/*" search string (assuming the separator is a slash).

In D503#5876, @dfaure wrote:

Thanks for the review.

However I can't push, do you know why? My SSH key in git.kolab.org looks correct.

BUILDS PASSED Harbormaster builds for the active diff completed successfully.
PUSHING Pushing changes to "origin/libkolab-1.0".
Exception: You do not have permission to push to this repository.
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.

My git remote for pushing is ssh://git@git.kolab.org/diffusion/LK/libkolab.git/
Did something change?

The changes of this patch have been incorporated into:
https://git.kolab.org/rG0849a45cb179763ed5a06c0ad3ddafb8455efeef

Implemented changerequests

See D411

See D411

Please note that I couldn't test this on my system. So only the development version is somewhat tested.

Same patch, but applied to feature/0.9-with-rebar2

Most likely candidate is:

outdated by now

I added the manually, thanks.

This has been implemented.

• The RID is null until the item has been first written to the server (but the resource will always first upload pending items before triggering a sync).
• There is no flag to indicate that an item has not been uploaded and I don't think there is a way to search for items that haven't been uploaded.

The above output only shows 3 SUBSCRIBE commands instead of the usual 4 in previous instances....,
and it never shows an UNSUBSCRIBE command. Needs to be investigated.

From the following debug output that was captured after the problem appeared, we can see that the notifications indeed seem to pile up in the NotificationManager for some reason.

dev/noRealMessageCount disables all codepaths that rely on the message count. If that performs adequately, then we could just be using that.

This is apparently a synchronization issue.
We're currently waiting for more information (see otrs).

In imap/retrieveitemstask.cpp:

With the latest version it is now possible to introspect the notificationManager with:

appendAndCompress only optimizes collection modifications, so that's not it.

Akonadiconsole subscribes in notificationmodel.cpp directly to dbus, so it's unlikely that this is the reason.

Some additional checks that could be done:

Given that we do see some unrelated sync operations including non-SILENT modifications in the log, but still no notifications in akonadiconsole we can conclude that this is a problem where the akonadiserver fails to send any notifications to any process.

In T1321#22196, @mollekopf wrote:

The current hypothesis is:

• The DataStore does a reestablishConnectionIfLost because we lost the connection to the mysql server while a transaction was ongoing.
• m_transactionLevel is never reset to 0 so remains > 0
• commitTransaction get's m_transactionLevel > 1 and thus never emits transactionComitted
• NotificationCollector::dispatchNotification is always in transaction and thus always enqueues new notifications, and never emits them since it's waiting on transactionCommitted.

DataStore is a thread-local singleton that also instantiates NotificationCollector which would explain why this behavior is observed only for the session of kontact.
It doesn't explain why a restart of kontact isn't enough to fix the situation though it seems?

The current hypothesis is:

• The DataStore does a reestablishConnectionIfLost because we lost the connection to the mysql server while a transaction was ongoing.
• m_transactionLevel is never reset to 0 so remains > 0
• commitTransaction get's m_transactionLevel > 1 and thus never emits transactionComitted
• NotificationCollector::dispatchNotification is always in transaction and thus always enqueues new notifications, and never emits them since it's waiting on transactionCommitted.

From the latest information provided (otrs 07/20/2016 13:03:24):

• The UID STORE +FLAGS command is successfully executed and we can see the FETCH (REV 2) response)
• The Job Tracker also reports the ItemModifyJob as successful
• No notifications at all are visible in the notification monitor
• The "INSERT INTO PimItemFlagRelation ..." command is successfully executed as recorded by the querydebugger.