From: David Bremner <david@tethera.net>
To: Gregor Zattler <telegraph@gmx.net>, notmuch <notmuch@notmuchmail.org>
Subject: Re: Bug: fatal error with notmuch new, second run starts indexing all over again
Date: Sun, 09 Jul 2017 11:35:27 -0300 [thread overview]
Message-ID: <87k23h3cgg.fsf@tethera.net> (raw)
In-Reply-To: <20170709142147.czeett6stskxrnkp@len.workgroup>
Gregor Zattler <telegraph@gmx.net> writes:
> Hi David,
> * David Bremner <david@tethera.net> [09. Jul. 2017]:
>> Gregor Zattler <telegraph@gmx.net> writes:
>>> Since its an email from an open mailing list I attach it to
>>> this very email.
>>>
>>
>> It might or might not be related, but I noticed that those two messages
>> get merged for me into a thread 1734 messages long of org-mode messages
>> (I have some old org messages, but I think I not the two you mention).
>>
>> I'm not sure yet if it's a bug in notmuch, or something strange about
>> mail from the org-mode list.
>
> This *might* be related with some other problem I reported
> regarding false threading of messages, as discussed in the thread
> containing amongst others id:874nvcekjk.fsf@qmul.ac.uk
>
> Short version: Some of the messages on this mailinglist had very
> weired References: headers mot probably causing notmuch to
> misbehave while threading the messages. But then there was no
> xapian exeption involved.
>
Right. I looks like there are indeed many message-ids in the resulting
database that look like valid email addresses. So that problem persists,
despite an attempted fix discussed in that thread.
I was wondering if the exception could result from overflowing some
internal limit due to threads many thousands of messages long. I will be
hard to know until I can replicate the exception. Perhaps a more
complete org-mode list archive would do it.
d
next prev parent reply other threads:[~2017-07-09 14:35 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-03 10:09 Bug: fatal error with notmuch new, second run starts indexing all over again Gregor Zattler
2017-07-03 10:46 ` David Bremner
2017-07-03 22:07 ` Gregor Zattler
2017-07-03 22:34 ` David Bremner
2017-07-05 16:46 ` Tomi Ollila
2017-07-06 9:31 ` Gregor Zattler
2017-07-09 12:36 ` David Bremner
2017-07-09 14:21 ` Gregor Zattler
2017-07-09 14:35 ` David Bremner [this message]
2017-07-13 7:04 ` Gregor Zattler
2017-07-13 10:31 ` David Bremner
2017-07-13 11:31 ` Gregor Zattler
2017-07-13 13:03 ` David Bremner
2017-07-13 13:59 ` Gregor Zattler
2017-07-13 18:26 ` David Bremner
2017-07-14 10:14 ` Gregor Zattler
2017-07-14 11:13 ` David Bremner
2017-07-14 21:27 ` Gregor Zattler
2018-07-01 15:36 ` Leonard Lausen
2018-07-03 21:57 ` Gregor Zattler
2018-07-08 2:07 ` David Bremner
2018-07-08 9:46 ` Gregor Zattler
2018-07-08 2:09 ` David Bremner
2018-07-09 15:31 ` Leonard Lausen
2018-07-10 11:11 ` David Bremner
2021-12-25 18:10 ` David Bremner
2021-12-27 19:05 ` confirmed (was: Bug: fatal error with notmuch new, second run starts indexing all over again) Gregor Zattler
2021-12-28 0:58 ` 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=87k23h3cgg.fsf@tethera.net \
--to=david@tethera.net \
--cc=notmuch@notmuchmail.org \
--cc=telegraph@gmx.net \
/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).