From e7baa8cdaa78a22fce6ef3fd7ab00cda2ce9d6ac Mon Sep 17 00:00:00 2001 From: Jim Nelson Date: Tue, 3 Sep 2013 17:47:47 -0700 Subject: [PATCH] More time for notification timing delay: Refs #6085 I noticed the double-archive problem again just now. Looking at the log, it took even longer than 250ms for Gmail to notify of the EXPUNGEs after the append, so this patch increases the delay to a full second. It may be that this delay strategy is only pushing the timing hole around, but until we can come up with a better solution, it'll have to do. --- src/engine/imap-engine/imap-engine-replay-queue.vala | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/engine/imap-engine/imap-engine-replay-queue.vala b/src/engine/imap-engine/imap-engine-replay-queue.vala index 441a09a4..085eaf1e 100644 --- a/src/engine/imap-engine/imap-engine-replay-queue.vala +++ b/src/engine/imap-engine/imap-engine-replay-queue.vala @@ -7,7 +7,7 @@ private class Geary.ImapEngine.ReplayQueue : Geary.BaseObject { // this value is high because delays between back-to-back unsolicited notifications have been // see as high as 250ms - private const int NOTIFICATION_QUEUE_WAIT_MSEC = 500; + private const int NOTIFICATION_QUEUE_WAIT_MSEC = 1000; private class ReplayClose : ReplayOperation { public ReplayClose() {