1 Return-Path: <bart@ursys.com.au>
\r
2 X-Original-To: notmuch@notmuchmail.org
\r
3 Delivered-To: notmuch@notmuchmail.org
\r
4 Received: from localhost (localhost [127.0.0.1])
\r
5 by olra.theworths.org (Postfix) with ESMTP id 0F333431FAF
\r
6 for <notmuch@notmuchmail.org>; Wed, 22 Aug 2012 18:43:25 -0700 (PDT)
\r
7 X-Virus-Scanned: Debian amavisd-new at olra.theworths.org
\r
11 X-Spam-Status: No, score=0 tagged_above=-999 required=5 tests=[none]
\r
13 Received: from olra.theworths.org ([127.0.0.1])
\r
14 by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024)
\r
15 with ESMTP id K7t5v14F3s6x for <notmuch@notmuchmail.org>;
\r
16 Wed, 22 Aug 2012 18:43:24 -0700 (PDT)
\r
17 Received: from bit.local (that.urnet.com.au [203.7.149.1])
\r
18 by olra.theworths.org (Postfix) with ESMTP id 0FF95431FAE
\r
19 for <notmuch@notmuchmail.org>; Wed, 22 Aug 2012 18:43:24 -0700 (PDT)
\r
20 Received: by bit.local (Postfix, from userid 501)
\r
21 id 1305112AB2AA; Thu, 23 Aug 2012 11:43:19 +1000 (EST)
\r
22 From: "Bart Bunting" <bart@ursys.com.au>
\r
23 To: Austin Clements <amdragon@MIT.EDU>
\r
24 Subject: Re: Errors after upgrade to 0.14
\r
25 In-Reply-To: <20120823013412.GX11179@mit.edu>
\r
26 References: <m2mx1m8pp3.fsf@ursys.com.au> <20120823004117.GT11179@mit.edu>
\r
27 <20120823010922.GV11179@mit.edu> <m2mx1m9zd9.fsf@ursys.com.au>
\r
28 <20120823013412.GX11179@mit.edu>
\r
29 User-Agent: Notmuch/0.13.2+128~g369b28d (http://notmuchmail.org)
\r
30 Emacs/24.2.50.1 (i386-apple-darwin12.0.0)
\r
31 Date: Thu, 23 Aug 2012 11:43:19 +1000
\r
32 Message-ID: <m2fw7etmbs.fsf@ursys.com.au>
\r
34 Content-Type: text/plain
\r
35 Cc: notmuch@notmuchmail.org
\r
36 X-BeenThere: notmuch@notmuchmail.org
\r
37 X-Mailman-Version: 2.1.13
\r
39 List-Id: "Use and development of the notmuch mail system."
\r
40 <notmuch.notmuchmail.org>
\r
41 List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,
\r
42 <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>
\r
43 List-Archive: <http://notmuchmail.org/pipermail/notmuch>
\r
44 List-Post: <mailto:notmuch@notmuchmail.org>
\r
45 List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>
\r
46 List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,
\r
47 <mailto:notmuch-request@notmuchmail.org?subject=subscribe>
\r
48 X-List-Received-Date: Thu, 23 Aug 2012 01:43:25 -0000
\r
52 I agree, it appears to be the normal locking issue.
\r
53 That poses a problem but one I'm used to.
\r
55 I was doing an archive when I hit the other error as well.
\r
57 I just got a debug traceback when entering the inbox from the hello
\r
58 screen. Unfortunately it locked up my entire emacs and had to kill the
\r
61 I'll keep trying until I get something more helpfull.
\r
69 Austin Clements <amdragon@MIT.EDU> writes:
\r
71 > This looks like a different error from the one in your original email.
\r
72 > Was the original error also triggered by hitting 'a'?
\r
74 > This error is definitely from simultaneous access to the database and
\r
75 > is expected. But this has been a problem since the dawn of notmuch
\r
76 > and shouldn't have started just with 0.14 (unless we did something to
\r
77 > make it worse?). I do have some experimental patches that fix the
\r
78 > database locking issues if it's turning out to be a serious problem
\r
79 > for you, but the fix introduces its own issues.
\r
81 > Quoth Bart Bunting on Aug 23 at 11:21 am:
\r
84 >> I applied the patch and this error was from after that.
\r
86 >> The way it was triggered was by hitting 'a' to archive a message in the
\r
89 >> From what I can tell it's just the xapian error and there is nothing
\r
90 >> about json. Hope it means more to you.
\r
92 >> 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
93 >> ad-Orig-signal(error ("A Xapian exception occurred opening database: Unable to get write lock on /Users/bart/mail/.notmuch/xapian: already locked"))
\r
94 >> signal(error ("A Xapian exception occurred opening database: Unable to get write lock on /Users/bart/mail/.notmuch/xapian: already locked"))
\r
95 >> ad-Orig-error("A Xapian exception occurred opening database: Unable to get write lock on /Users/bart/mail/.notmuch/xapian: already locked")
\r
96 >> apply(ad-Orig-error "A Xapian exception occurred opening database: Unable to get write lock on /Users/bart/mail/.notmuch/xapian: already locked")
\r
97 >> error("A Xapian exception occurred opening database: Unable to get write lock on /Users/bart/mail/.notmuch/xapian: already locked")
\r
98 >> notmuch-call-notmuch-process("tag" "-inbox" "--" "thread:00000000000225c8")
\r
99 >> apply(notmuch-call-notmuch-process "tag" ("-inbox" "--" "thread:00000000000225c8"))
\r
100 >> notmuch-tag("thread:00000000000225c8" ("-inbox"))
\r
101 >> notmuch-search-tag-region(800 800 ("-inbox"))
\r
102 >> notmuch-search-tag(("-inbox"))
\r
103 >> ad-Orig-notmuch-search-archive-thread()
\r
104 >> notmuch-search-archive-thread()
\r
105 >> call-interactively(notmuch-search-archive-thread nil nil)
\r
110 >> Austin Clements <amdragon@MIT.EDU> writes:
\r
112 >> > Quoth myself on Aug 22 at 8:41 pm:
\r
113 >> >> Quoth Bart Bunting on Aug 23 at 9:36 am:
\r
114 >> >> > Good morning,
\r
116 >> >> > After upgrading to notmuch 014 I am seeing the following messages appear
\r
117 >> >> > in the messages buffer.
\r
119 >> >> > error in process filter: byte-code: Wrong type argument: number-or-marker-p, nil
\r
120 >> >> > error in process filter: Wrong type argument: number-or-marker-p, nil
\r
122 >> >> > I am also getting a repeating message in the minibuffer (I think) which
\r
123 >> >> > says something like "json read tail error". Sorry that I am not more
\r
124 >> >> > specific as I use emacspeak and this message appears to repeat many
\r
125 >> >> > times interupting speech so I am not 100% sure of what it exactly says.
\r
127 >> >> This is probably "json-readtable-error", which is, unfortunately,
\r
128 >> >> about the most generic error the JSON parser can give.
\r
130 >> >> > My gut feeling is that it is happening when notmuch is updating the
\r
131 >> >> > database or something.
\r
133 >> >> > Is this expected behaviour? It is particularly annoying for me as it
\r
134 >> >> > sends the speech synth crazy and crashes it for a period of about 30
\r
137 >> >> > If it is expected then I will try and find a way to prevent emacspeak
\r
138 >> >> > from trying to read it.
\r
140 >> >> This is definitely not expected behavior. Does this happen when
\r
141 >> >> you're searching for messages or when you're viewing a thread? Can
\r
142 >> >> you give any more details on what you're doing when you get this
\r
145 >> >> Try doing M-x toggle-debug-on-error and then triggering the error.
\r
146 >> >> Hopefully Emacs will give you a buffer with a backtrace that will give
\r
147 >> >> us a better idea of where this is happening.
\r
149 >> > Actually, I might know what's going on here. Based on your suspicion
\r
150 >> > about notmuch updating the database and assuming that this happens in
\r
151 >> > the search buffer, I think the parser error recovery code is leaving
\r
152 >> > the parser in a slightly invalid state, which causes the next
\r
153 >> > invocation to think it can consume more data when there is no more
\r
154 >> > data to consume. I would expect that to give at most one readtable
\r
155 >> > error, but maybe there's something I'm overlooking.
\r
157 >> > Could you try the following one line patch?
\r
159 >> > diff --git a/emacs/notmuch-lib.el b/emacs/notmuch-lib.el
\r
160 >> > index 900235b..a09c0f6 100644
\r
161 >> > --- a/emacs/notmuch-lib.el
\r
162 >> > +++ b/emacs/notmuch-lib.el
\r
163 >> > @@ -375,7 +375,7 @@ resynchronize after an error by moving point."
\r
165 >> > (if (eq (notmuch-json-next jp) 'value)
\r
166 >> > ;; We're already at a value
\r
168 >> > + (if (eobp) 'retry nil)
\r
169 >> > ;; Drive the state toward 'expect-value
\r
170 >> > (skip-chars-forward " \t\r\n")
\r
171 >> > (or (when (eobp) 'retry)
\r
175 Bart Bunting - Engineering Manager - URSYS
\r
176 459-461 Parramatta Rd. Leichhardt NSW 2040 Australia
\r
177 Ph: +61 2 8745 2811
\r