From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from localhost (localhost [127.0.0.1]) by arlo.cworth.org (Postfix) with ESMTP id 72A616DE26AF for ; Mon, 19 Mar 2018 13:03:26 -0700 (PDT) X-Virus-Scanned: Debian amavisd-new at cworth.org X-Spam-Flag: NO X-Spam-Score: 0 X-Spam-Level: X-Spam-Status: No, score=0 tagged_above=-999 required=5 tests=[AWL=0.011, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=disabled Received: from arlo.cworth.org ([127.0.0.1]) by localhost (arlo.cworth.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4-qoAxqtmVTW for ; Mon, 19 Mar 2018 13:03:25 -0700 (PDT) Received: from fethera.tethera.net (fethera.tethera.net [198.245.60.197]) by arlo.cworth.org (Postfix) with ESMTPS id 6BB126DE26AA for ; Mon, 19 Mar 2018 13:03:25 -0700 (PDT) Received: from remotemail by fethera.tethera.net with local (Exim 4.89) (envelope-from ) id 1ey108-0002or-7a; Mon, 19 Mar 2018 16:03:24 -0400 Received: (nullmailer pid 27842 invoked by uid 1000); Mon, 19 Mar 2018 20:03:21 -0000 From: David Bremner To: Antoine =?utf-8?Q?Beaupr=C3=A9?= , notmuch@notmuchmail.org Cc: xapian-discuss@lists.xapian.org Subject: Re: bug: "no top level messages" crash on Zen email loops In-Reply-To: <87a7v42bv9.fsf@curie.anarc.at> References: <87d10042pu.fsf@curie.anarc.at> <87woy8vx7i.fsf@tesseract.cs.unb.ca> <87a7v42bv9.fsf@curie.anarc.at> X-List-To: notmuch Date: Mon, 19 Mar 2018 17:03:21 -0300 Message-ID: <87r2ofx27q.fsf@tesseract.cs.unb.ca> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-BeenThere: notmuch@notmuchmail.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: "Use and development of the notmuch mail system." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Mar 2018 20:03:26 -0000 Antoine Beaupr=C3=A9 writes: > On 2018-03-19 13:36:49, David Bremner wrote: >> >> I can't duplicate that part.=20=20 > > That's very strange. I can reproduce this on my workstation here, but > taking the tarball I sent in the original message, I can't reproduce > anymore. So something changed! I suspect it's the "flags" on the > message. I have "F" everywhere because I'm experimenting with syncing > (badly) my inbox tag everywhere, through the flagged tag. All post-new > hooks stuff that shouldn't affect this because it's in a new > environment, but it does change the flag on the files sometimes. > > So attached is a *new* reproducer, with which I *can* reproduce in a > clean VM with notmuch from stretch (0.23?). I can confirm this reproduces both the xapian-check and the notmuch-show error. Olly agrees that whatever notmuch is doing wrong, it shouldn't lead to a corrupted database (unless we reach around the API and access files directly, which I don't think we do). d