From: "Antoine Beaupré" <anarcat@orangeseeds.org>
To: Olly Betts <olly@survex.com>, David Bremner <david@tethera.net>
Cc: notmuch@notmuchmail.org, xapian-discuss@lists.xapian.org
Subject: Re: bug: "no top level messages" crash on Zen email loops
Date: Thu, 29 Mar 2018 08:50:22 -0400 [thread overview]
Message-ID: <87efk359m9.fsf@curie.anarc.at> (raw)
In-Reply-To: <20180329031721.GA31208@survex.com>
On 2018-03-29 04:17:21, Olly Betts wrote:
> On Mon, Mar 19, 2018 at 05:03:21PM -0300, David Bremner wrote:
>> 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
>
> There was a Xapian bug here, which I fixed on master last week and will
> be fixed in 1.4.6.
An honor. It's not every day you find a bug in a database software. ;)
> If changes to a new database which didn't modify the termlist table were
> committed, then a disk block which had been allocated to be the root
> block in the termlist table was leaked (not used but not on the
> freelist of blocks the table can recycle). This was largely harmless,
> except that it was detected by Database::check() and caused an error.
Hmm... but if I understand correctly, that's one part of the story: I
could get that error and not have the problem with `notmuch show`. Does
that *also* resolve the issue with email loops?
A.
--
Travail, du latin Tri Palium trois pieux, instrument de torture.
next prev parent reply other threads:[~2018-03-29 12:50 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 ` bug: "no top level messages" crash on Zen email loops David Bremner
2018-03-29 3:17 ` Olly Betts
2018-03-29 12:50 ` Antoine Beaupré [this message]
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=87efk359m9.fsf@curie.anarc.at \
--to=anarcat@orangeseeds.org \
--cc=david@tethera.net \
--cc=notmuch@notmuchmail.org \
--cc=olly@survex.com \
--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).