From: David Bremner <david@tethera.net>
To: "Antoine Beaupré" <anarcat@orangeseeds.org>, notmuch@notmuchmail.org
Cc: xapian-discuss@lists.xapian.org
Subject: Re: bug: "no top level messages" crash on Zen email loops
Date: Mon, 19 Mar 2018 17:03:21 -0300 [thread overview]
Message-ID: <87r2ofx27q.fsf@tesseract.cs.unb.ca> (raw)
In-Reply-To: <87a7v42bv9.fsf@curie.anarc.at>
Antoine Beaupré <anarcat@orangeseeds.org> writes:
> On 2018-03-19 13:36:49, David Bremner wrote:
>>
>> I can't duplicate that part.
>
> 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
next prev parent reply other threads:[~2018-03-19 20:03 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-19 13:25 bug: "no top level messages" crash on Zen email loops Antoine Beaupré
2018-03-19 16:36 ` David Bremner
2018-03-19 17:50 ` Antoine Beaupré
2018-03-19 17:56 ` Antoine Beaupré
2018-03-19 19:25 ` tip: how to not forget attachments Antoine Beaupré
2018-03-19 19:57 ` Brian Sniffen
2018-03-19 20:16 ` Antoine Beaupré
2018-03-19 21:40 ` Brian Sniffen
2018-03-19 21:47 ` Antoine Beaupré
2018-03-19 20:03 ` David Bremner [this message]
2018-03-29 3:17 ` bug: "no top level messages" crash on Zen email loops Olly Betts
2018-03-29 12:50 ` Antoine Beaupré
2018-03-29 16:31 ` David Bremner
2018-03-30 4:35 ` Olly Betts
2018-03-20 21:22 ` [PATCH 1/2] test: two new messages for the 'broken' corpus David Bremner
2018-03-20 21:22 ` [PATCH 2/2] test: add known broken test for indexing an In-Reply-To loop David Bremner
2018-03-20 22:09 ` Tomi Ollila
2018-03-21 1:34 ` David Bremner
2018-04-02 11:03 ` [PATCH] WIP: test patch for reference loop problem David Bremner
2018-04-13 0:10 ` Antoine Beaupré
2018-04-13 11:17 ` David Bremner
2018-04-28 13:28 ` bug: "no top level messages" crash on Zen email loops David Bremner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87r2ofx27q.fsf@tesseract.cs.unb.ca \
--to=david@tethera.net \
--cc=anarcat@orangeseeds.org \
--cc=notmuch@notmuchmail.org \
--cc=xapian-discuss@lists.xapian.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://yhetil.org/notmuch.git/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).