Re: Errors after upgrade to 0.14
authorAustin Clements <amdragon@MIT.EDU>
Thu, 23 Aug 2012 00:41:17 +0000 (20:41 +2000)
committerW. Trevor King <wking@tremily.us>
Fri, 7 Nov 2014 17:49:11 +0000 (09:49 -0800)
8e/ca7e690967c0ee9424772925c088309b3db7b3 [new file with mode: 0644]

diff --git a/8e/ca7e690967c0ee9424772925c088309b3db7b3 b/8e/ca7e690967c0ee9424772925c088309b3db7b3
new file mode 100644 (file)
index 0000000..87059a4
--- /dev/null
@@ -0,0 +1,111 @@
+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 B9B27431FAF\r
+       for <notmuch@notmuchmail.org>; Wed, 22 Aug 2012 17:41:22 -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 DNdDmnA9s0tG for <notmuch@notmuchmail.org>;\r
+       Wed, 22 Aug 2012 17:41:22 -0700 (PDT)\r
+Received: from dmz-mailsec-scanner-5.mit.edu (DMZ-MAILSEC-SCANNER-5.MIT.EDU\r
+       [18.7.68.34])\r
+       by olra.theworths.org (Postfix) with ESMTP id 36BC0431FAE\r
+       for <notmuch@notmuchmail.org>; Wed, 22 Aug 2012 17:41:22 -0700 (PDT)\r
+X-AuditID: 12074422-b7f1f6d00000090b-f3-50357c304223\r
+Received: from mailhub-auth-4.mit.edu ( [18.7.62.39])\r
+       by dmz-mailsec-scanner-5.mit.edu (Symantec Messaging Gateway) with SMTP\r
+       id 5A.AC.02315.03C75305; Wed, 22 Aug 2012 20:41:20 -0400 (EDT)\r
+Received: from outgoing.mit.edu (OUTGOING-AUTH.MIT.EDU [18.7.22.103])\r
+       by mailhub-auth-4.mit.edu (8.13.8/8.9.2) with ESMTP id q7N0fJvl017362; \r
+       Wed, 22 Aug 2012 20:41:20 -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 q7N0fHkO014904\r
+       (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NOT);\r
+       Wed, 22 Aug 2012 20:41:19 -0400 (EDT)\r
+Received: from amthrax by awakening.csail.mit.edu with local (Exim 4.77)\r
+       (envelope-from <amdragon@mit.edu>)\r
+       id 1T4LU5-0000Ws-5m; Wed, 22 Aug 2012 20:41:17 -0400\r
+Date: Wed, 22 Aug 2012 20:41:17 -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: <20120823004117.GT11179@mit.edu>\r
+References: <m2mx1m8pp3.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: <m2mx1m8pp3.fsf@ursys.com.au>\r
+User-Agent: Mutt/1.5.21 (2010-09-15)\r
+X-Brightmail-Tracker:\r
+ H4sIAAAAAAAAA+NgFmpkleLIzCtJLcpLzFFi42IRYrdT1zWoMQ0wOLLDyuLinv3sFtdvzmR2\r
+       YPJ4tuoWs8epL4fYA5iiuGxSUnMyy1KL9O0SuDKunbvJWvCKu+Lf9oAGxg2cXYycHBICJhK7\r
+       D79hh7DFJC7cW8/WxcjFISSwj1Hi6Z8VTCAJIYENjBI3lhRAJE4ySRw8NwmqagmjxOHOTSwg\r
+       VSwCqhLd606DjWIT0JDYtn85YxcjB4eIgIrEkR18IGFmAWmJb7+bwYYKC2hKHOu5wgpi8wro\r
+       SLxcs4oZYpmmRMuBq1BxQYmTM5+wQPRqSdz495IJZCTInOX/OEDCnEDhn7dng5WLAm2acnIb\r
+       2wRGoVlIumch6Z6F0L2AkXkVo2xKbpVubmJmTnFqsm5xcmJeXmqRrqlebmaJXmpK6SZGcEi7\r
+       KO1g/HlQ6RCjAAejEg/vC3PTACHWxLLiytxDjJIcTEqivF8qgEJ8SfkplRmJxRnxRaU5qcWH\r
+       GCU4mJVEeLuKgHK8KYmVValF+TApaQ4WJXHeayk3/YUE0hNLUrNTUwtSi2CyMhwcShK81dVA\r
+       jYJFqempFWmZOSUIaSYOTpDhPEDDM0FqeIsLEnOLM9Mh8qcYFaXEeR1AEgIgiYzSPLheWMp5\r
+       xSgO9IowbzpIFQ8wXcF1vwIazAQ0WO2qMcjgkkSElFQD46o0ESFGi+XvswJvxuVub4n/n8r/\r
+       2n+vQ/NVxSyBKq0jZ8WU5zbYKPCGFl8NMJPZ83CT6TyTg2qNV44dVFFxlv9rfldXvXaZc03i\r
+       Lzb+r25Pon4c/mnBe+HdpynH2iY17c9njdLuW++s3nHC+phtyVeX6bLX7Epyd5vtdxWxt323\r
+       oNz4cI+DEktxRqKhFnNRcSIA5Q4X0xQDAAA=\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 00:41:22 -0000\r
+\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