--- /dev/null
+Return-Path: <amdragon@mit.edu>\r
+X-Original-To: notmuch@notmuchmail.org\r
+Delivered-To: notmuch@notmuchmail.org\r
+Received: from localhost (localhost [127.0.0.1])\r
+ by olra.theworths.org (Postfix) with ESMTP id DC13D431FAF\r
+ for <notmuch@notmuchmail.org>; Wed, 22 Aug 2012 18:34:16 -0700 (PDT)\r
+X-Virus-Scanned: Debian amavisd-new at olra.theworths.org\r
+X-Spam-Flag: NO\r
+X-Spam-Score: -0.7\r
+X-Spam-Level: \r
+X-Spam-Status: No, score=-0.7 tagged_above=-999 required=5\r
+ tests=[RCVD_IN_DNSWL_LOW=-0.7] autolearn=disabled\r
+Received: from olra.theworths.org ([127.0.0.1])\r
+ by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024)\r
+ with ESMTP id Ektz6Y1wQEdX for <notmuch@notmuchmail.org>;\r
+ Wed, 22 Aug 2012 18:34:16 -0700 (PDT)\r
+Received: from dmz-mailsec-scanner-7.mit.edu (DMZ-MAILSEC-SCANNER-7.MIT.EDU\r
+ [18.7.68.36])\r
+ by olra.theworths.org (Postfix) with ESMTP id DFDFF431FAE\r
+ for <notmuch@notmuchmail.org>; Wed, 22 Aug 2012 18:34:15 -0700 (PDT)\r
+X-AuditID: 12074424-b7fa06d0000008c2-c1-503588979310\r
+Received: from mailhub-auth-3.mit.edu ( [18.9.21.43])\r
+ by dmz-mailsec-scanner-7.mit.edu (Symantec Messaging Gateway) with SMTP\r
+ id A8.0E.02242.79885305; Wed, 22 Aug 2012 21:34:15 -0400 (EDT)\r
+Received: from outgoing.mit.edu (OUTGOING-AUTH.MIT.EDU [18.7.22.103])\r
+ by mailhub-auth-3.mit.edu (8.13.8/8.9.2) with ESMTP id q7N1YDAK015517; \r
+ Wed, 22 Aug 2012 21:34:14 -0400\r
+Received: from awakening.csail.mit.edu (awakening.csail.mit.edu [18.26.4.91])\r
+ (authenticated bits=0)\r
+ (User authenticated as amdragon@ATHENA.MIT.EDU)\r
+ by outgoing.mit.edu (8.13.6/8.12.4) with ESMTP id q7N1YC8f019546\r
+ (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NOT);\r
+ Wed, 22 Aug 2012 21:34:13 -0400 (EDT)\r
+Received: from amthrax by awakening.csail.mit.edu with local (Exim 4.77)\r
+ (envelope-from <amdragon@mit.edu>)\r
+ id 1T4MJI-0000eQ-56; Wed, 22 Aug 2012 21:34:12 -0400\r
+Date: Wed, 22 Aug 2012 21:34:12 -0400\r
+From: Austin Clements <amdragon@MIT.EDU>\r
+To: Bart Bunting <bart@ursys.com.au>\r
+Subject: Re: Errors after upgrade to 0.14\r
+Message-ID: <20120823013412.GX11179@mit.edu>\r
+References: <m2mx1m8pp3.fsf@ursys.com.au> <20120823004117.GT11179@mit.edu>\r
+ <20120823010922.GV11179@mit.edu> <m2mx1m9zd9.fsf@ursys.com.au>\r
+MIME-Version: 1.0\r
+Content-Type: text/plain; charset=us-ascii\r
+Content-Disposition: inline\r
+In-Reply-To: <m2mx1m9zd9.fsf@ursys.com.au>\r
+User-Agent: Mutt/1.5.21 (2010-09-15)\r
+X-Brightmail-Tracker:\r
+ H4sIAAAAAAAAA+NgFmphleLIzCtJLcpLzFFi42IR4hTV1p3eYRpgsGemsMXFPfvZLa7fnMns\r
+ wOTxbNUtZo9TXw6xBzBFcdmkpOZklqUW6dslcGUcWLCHueCFesXpqdeZGhjvyncxcnJICJhI\r
+ 3NxynRnCFpO4cG89WxcjF4eQwD5Gid/zvrFDOBsYJaY93gaVOckksX3rXSYIZwmjxIKNu8H6\r
+ WQRUJXYdO8cCYrMJaEhs27+csYuRg0NEQEXiyA4+kDCzgLTEt9/NTCC2sICmxLGeK6wgNq+A\r
+ jsSt9yehFvQzSnz6cIYFIiEocXLmExaIZi2JG/9eMoHMBBm0/B8HSJgTKHzm6RywmaJAq6ac\r
+ 3MY2gVFoFpLuWUi6ZyF0L2BkXsUom5JbpZubmJlTnJqsW5ycmJeXWqRrrpebWaKXmlK6iREU\r
+ 2OwuKjsYmw8pHWIU4GBU4uF9YW4aIMSaWFZcmXuIUZKDSUmUV7QdKMSXlJ9SmZFYnBFfVJqT\r
+ WnyIUYKDWUmE9081UI43JbGyKrUoHyYlzcGiJM57PeWmv5BAemJJanZqakFqEUxWhoNDSYLX\r
+ EBjBQoJFqempFWmZOSUIaSYOTpDhPEDDpUFqeIsLEnOLM9Mh8qcYFaXEedlAEgIgiYzSPLhe\r
+ WOJ5xSgO9Iow7wqQu3mASQuu+xXQYCagwWpXjUEGlyQipKQaGAX4k7bzmTVN1FHWP9L30/9k\r
+ 7drzF1PYnFIuWp353dnx8OZne8Vp589HV1a9aov6df9wYEeiifKxl3tc5gVtan9Uz+hQtC75\r
+ tsr5EokuYe8ADwn7qRyCmRcb256xXbvkN6vB5E9nZFGlY9bEr2py3jILlJfJ7f6xqTy/mGf6\r
+ NJUTb6rZb+S1K7EUZyQaajEXFScCANmAhyoXAwAA\r
+Cc: notmuch@notmuchmail.org\r
+X-BeenThere: notmuch@notmuchmail.org\r
+X-Mailman-Version: 2.1.13\r
+Precedence: list\r
+List-Id: "Use and development of the notmuch mail system."\r
+ <notmuch.notmuchmail.org>\r
+List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,\r
+ <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>\r
+List-Archive: <http://notmuchmail.org/pipermail/notmuch>\r
+List-Post: <mailto:notmuch@notmuchmail.org>\r
+List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>\r
+List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,\r
+ <mailto:notmuch-request@notmuchmail.org?subject=subscribe>\r
+X-List-Received-Date: Thu, 23 Aug 2012 01:34:17 -0000\r
+\r
+This looks like a different error from the one in your original email.\r
+Was the original error also triggered by hitting 'a'?\r
+\r
+This error is definitely from simultaneous access to the database and\r
+is expected. But this has been a problem since the dawn of notmuch\r
+and shouldn't have started just with 0.14 (unless we did something to\r
+make it worse?). I do have some experimental patches that fix the\r
+database locking issues if it's turning out to be a serious problem\r
+for you, but the fix introduces its own issues.\r
+\r
+Quoth Bart Bunting on Aug 23 at 11:21 am:\r
+> Hi Austin,\r
+> \r
+> I applied the patch and this error was from after that.\r
+> \r
+> The way it was triggered was by hitting 'a' to archive a message in the\r
+> search view.\r
+> \r
+> From what I can tell it's just the xapian error and there is nothing\r
+> about json. Hope it means more to you.\r
+> \r
+> Debugger entered--Lisp error: (error "A Xapian exception occurred opening database: Unable to get write lock on /Users/bart/mail/.notmuch/xapian: already locked")\r
+> ad-Orig-signal(error ("A Xapian exception occurred opening database: Unable to get write lock on /Users/bart/mail/.notmuch/xapian: already locked"))\r
+> signal(error ("A Xapian exception occurred opening database: Unable to get write lock on /Users/bart/mail/.notmuch/xapian: already locked"))\r
+> ad-Orig-error("A Xapian exception occurred opening database: Unable to get write lock on /Users/bart/mail/.notmuch/xapian: already locked")\r
+> apply(ad-Orig-error "A Xapian exception occurred opening database: Unable to get write lock on /Users/bart/mail/.notmuch/xapian: already locked")\r
+> error("A Xapian exception occurred opening database: Unable to get write lock on /Users/bart/mail/.notmuch/xapian: already locked")\r
+> notmuch-call-notmuch-process("tag" "-inbox" "--" "thread:00000000000225c8")\r
+> apply(notmuch-call-notmuch-process "tag" ("-inbox" "--" "thread:00000000000225c8"))\r
+> notmuch-tag("thread:00000000000225c8" ("-inbox"))\r
+> notmuch-search-tag-region(800 800 ("-inbox"))\r
+> notmuch-search-tag(("-inbox"))\r
+> ad-Orig-notmuch-search-archive-thread()\r
+> notmuch-search-archive-thread()\r
+> call-interactively(notmuch-search-archive-thread nil nil)\r
+> \r
+> \r
+> Kind regards\r
+> \r
+> Austin Clements <amdragon@MIT.EDU> writes:\r
+> \r
+> > Quoth myself on Aug 22 at 8:41 pm:\r
+> >> Quoth Bart Bunting on Aug 23 at 9:36 am:\r
+> >> > Good morning,\r
+> >> > \r
+> >> > After upgrading to notmuch 014 I am seeing the following messages appear\r
+> >> > in the messages buffer.\r
+> >> > \r
+> >> > error in process filter: byte-code: Wrong type argument: number-or-marker-p, nil\r
+> >> > error in process filter: Wrong type argument: number-or-marker-p, nil\r
+> >> > \r
+> >> > I am also getting a repeating message in the minibuffer (I think) which\r
+> >> > says something like "json read tail error". Sorry that I am not more\r
+> >> > specific as I use emacspeak and this message appears to repeat many\r
+> >> > times interupting speech so I am not 100% sure of what it exactly says.\r
+> >> \r
+> >> This is probably "json-readtable-error", which is, unfortunately,\r
+> >> about the most generic error the JSON parser can give.\r
+> >> \r
+> >> > My gut feeling is that it is happening when notmuch is updating the\r
+> >> > database or something.\r
+> >> > \r
+> >> > Is this expected behaviour? It is particularly annoying for me as it\r
+> >> > sends the speech synth crazy and crashes it for a period of about 30\r
+> >> > seconds.\r
+> >> > \r
+> >> > If it is expected then I will try and find a way to prevent emacspeak\r
+> >> > from trying to read it.\r
+> >> \r
+> >> This is definitely not expected behavior. Does this happen when\r
+> >> you're searching for messages or when you're viewing a thread? Can\r
+> >> you give any more details on what you're doing when you get this\r
+> >> error?\r
+> >> \r
+> >> Try doing M-x toggle-debug-on-error and then triggering the error.\r
+> >> Hopefully Emacs will give you a buffer with a backtrace that will give\r
+> >> us a better idea of where this is happening.\r
+> >\r
+> > Actually, I might know what's going on here. Based on your suspicion\r
+> > about notmuch updating the database and assuming that this happens in\r
+> > the search buffer, I think the parser error recovery code is leaving\r
+> > the parser in a slightly invalid state, which causes the next\r
+> > invocation to think it can consume more data when there is no more\r
+> > data to consume. I would expect that to give at most one readtable\r
+> > error, but maybe there's something I'm overlooking.\r
+> >\r
+> > Could you try the following one line patch?\r
+> >\r
+> > diff --git a/emacs/notmuch-lib.el b/emacs/notmuch-lib.el\r
+> > index 900235b..a09c0f6 100644\r
+> > --- a/emacs/notmuch-lib.el\r
+> > +++ b/emacs/notmuch-lib.el\r
+> > @@ -375,7 +375,7 @@ resynchronize after an error by moving point."\r
+> > \r
+> > (if (eq (notmuch-json-next jp) 'value)\r
+> > ;; We're already at a value\r
+> > - nil\r
+> > + (if (eobp) 'retry nil)\r
+> > ;; Drive the state toward 'expect-value\r
+> > (skip-chars-forward " \t\r\n")\r
+> > (or (when (eobp) 'retry)\r
+> >\r
projects / notmuch-archives.git / commitdiff