--- /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 15191431FAF\r
+ for <notmuch@notmuchmail.org>; Wed, 22 Aug 2012 18:09:27 -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 QBNzjSW5ysxt for <notmuch@notmuchmail.org>;\r
+ Wed, 22 Aug 2012 18:09:26 -0700 (PDT)\r
+Received: from dmz-mailsec-scanner-4.mit.edu (DMZ-MAILSEC-SCANNER-4.MIT.EDU\r
+ [18.9.25.15])\r
+ by olra.theworths.org (Postfix) with ESMTP id 6C7CA431FAE\r
+ for <notmuch@notmuchmail.org>; Wed, 22 Aug 2012 18:09:26 -0700 (PDT)\r
+X-AuditID: 1209190f-b7f306d0000008b4-33-503582c52b3e\r
+Received: from mailhub-auth-1.mit.edu ( [18.9.21.35])\r
+ by dmz-mailsec-scanner-4.mit.edu (Symantec Messaging Gateway) with SMTP\r
+ id 3F.71.02228.5C285305; Wed, 22 Aug 2012 21:09:25 -0400 (EDT)\r
+Received: from outgoing.mit.edu (OUTGOING-AUTH.MIT.EDU [18.7.22.103])\r
+ by mailhub-auth-1.mit.edu (8.13.8/8.9.2) with ESMTP id q7N19Omm019691; \r
+ Wed, 22 Aug 2012 21:09:25 -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 q7N19N6u017455\r
+ (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NOT);\r
+ Wed, 22 Aug 2012 21:09:24 -0400 (EDT)\r
+Received: from amthrax by awakening.csail.mit.edu with local (Exim 4.77)\r
+ (envelope-from <amdragon@MIT.EDU>)\r
+ id 1T4LvG-0000b0-Vc; Wed, 22 Aug 2012 21:09:23 -0400\r
+Date: Wed, 22 Aug 2012 21:09:22 -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: <20120823010922.GV11179@mit.edu>\r
+References: <m2mx1m8pp3.fsf@ursys.com.au>\r
+ <20120823004117.GT11179@mit.edu>\r
+MIME-Version: 1.0\r
+Content-Type: text/plain; charset=us-ascii\r
+Content-Disposition: inline\r
+In-Reply-To: <20120823004117.GT11179@mit.edu>\r
+User-Agent: Mutt/1.5.21 (2010-09-15)\r
+X-Brightmail-Tracker:\r
+ H4sIAAAAAAAAA+NgFmpileLIzCtJLcpLzFFi42IR4hRV1j3aZBpgsGWxtcXFPfvZLa7fnMns\r
+ wOTxbNUtZo9TXw6xBzBFcdmkpOZklqUW6dslcGU0n1/CVjBfpKLz0BHWBsYX/F2MnBwSAiYS\r
+ +5puskHYYhIX7q0Hsrk4hAT2MUq8vPCCCcLZwChx+cNbqMxJJomnR++xQzhLGCXapk5lBOln\r
+ EVCVePnvNAuIzSagIbFt/3KgOAeHiICKxJEdfCBhZgFpiW+/m5lAbGEBTYljPVdYQUp4BXQk\r
+ zn3OBwkLCfhIrJy3hhnE5hUQlDg58wkLRKuWxI1/L5lAykHGLP/HARLmFNCVODnjDCuILQq0\r
+ aMrJbWwTGIVmIemehaR7FkL3AkbmVYyyKblVurmJmTnFqcm6xcmJeXmpRbomermZJXqpKaWb\r
+ GMFBLcm/g/HbQaVDjAIcjEo8vC/MTQOEWBPLiitzDzFKcjApifL+aAAK8SXlp1RmJBZnxBeV\r
+ 5qQWH2KU4GBWEuH9Uw2U401JrKxKLcqHSUlzsCiJ815NuekvJJCeWJKanZpakFoEk5Xh4FCS\r
+ 4HUHRq+QYFFqempFWmZOCUKaiYMTZDgP0HBrkBre4oLE3OLMdIj8KUZFKXHeCJCEAEgiozQP\r
+ rheWdF4xigO9IgzRzgNMWHDdr4AGMwENVrtqDDK4JBEhJdXAmOiXNdXA4V77sV3Smy/cc3FQ\r
+ Fa9U9m73sjn4dsHk4sT9qTd87BszNZxbFxf6Tmlm/OhmG2relKqq8yrkxsk7MXaba06cvOjw\r
+ uWJ5KnMDq5Nk9R4e15DPxxz93hamtP5Zo37EaS3PBikPC/W53lsL8pq+Si6yWXPwg1Jb3ML/\r
+ y3o+mtUyTJdVYinOSDTUYi4qTgQAcDmCWBUDAAA=\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:09:27 -0000\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