unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: David Bremner <david@tethera.net>
To: "Naveen N. Rao" <naveen.n.rao@linux.vnet.ibm.com>,
	notmuch@notmuchmail.org
Subject: Re: 'notmuch search thread:<>' lists multiple threads
Date: Sun, 08 Apr 2018 00:04:35 -0300	[thread overview]
Message-ID: <87sh86v1oc.fsf@tethera.net> (raw)
In-Reply-To: <1523007700.l8xm6nm6af.naveen@linux.ibm.com>

"Naveen N. Rao" <naveen.n.rao@linux.vnet.ibm.com> writes:

> Greetings--
> If I search for threads matching a specific thread-id, I am seeing 
> multiple results:
>
> $ notmuch search --output=threads thread:00000000000c4d20
> thread:00000000000c4d1e
> thread:00000000000c4d20

This looks like a bug to me. I was able to replicate it in my own mail
store with the script at the end of the message. I haven't completely
analyzed the situation yet, but one thing I noticed is that in all
"bad threads", there are files with duplicate message-ids. Typical
output looks like

╭─ zancas:software/upstream/notmuch/test 
╰─ (git)-[master]-% notmuch search thread:000000000001760a
thread:00000000000175e5  November 03 [1/2(3)] 128@gmx.us; Bug#846042: VTK 8 (unread)
thread:000000000001760a   2016-11-27 [1/2(3)] 128@gmx.us; Bug#846042: virtual/meta package for python-vtk (unread)

At least some of this mail data is public, but I'm not sure if the bad
threading is reproducible or not; I want to run a complete census
overnight before I reindex.

Even if the bug is non-deterministic, it probably lives in lib/add-message.cc

----------------------------------------------------------------------

count=0
success=0
for id in $(notmuch search --output=threads '*'); do
    count=$((count +1))
    matches=$((`notmuch search --output=threads "$id" | wc -l`))
    if [ "$matches" = 1 ]; then
	success=$((success + 1))
    else
        echo "bad thread: $id"
    fi
    if [ $((count % 1000)) -eq 0 ]; then
        echo $count;
    fi
done

echo "count=$count success=$success"

  parent reply	other threads:[~2018-04-08  3:04 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-06  9:46 'notmuch search thread:<>' lists multiple threads Naveen N. Rao
2018-04-06 10:23 ` Naveen N. Rao
2018-04-08  3:04 ` David Bremner [this message]
2018-04-09 11:54   ` David Bremner
2018-04-10  1:45     ` [PATCH] devel: add new tool to draw thread structure David Bremner
2018-10-08  3:30       ` Daniel Kahn Gillmor
2018-04-18 10:18     ` 'notmuch search thread:<>' lists multiple threads Naveen N. Rao
2018-04-22  0:45       ` David Bremner
2018-06-28 10:36         ` Naveen N. Rao
2018-06-30 13:42           ` David Bremner
2018-08-30 12:52             ` David Bremner
2018-09-06 10:50               ` Naveen N. Rao
2019-06-27 14:45                 ` Naveen N. Rao
2019-06-27 14:53                   ` Naveen N. Rao
2021-12-23 18:00       ` David Bremner
2022-01-14 11:26         ` Naveen N. Rao

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=87sh86v1oc.fsf@tethera.net \
    --to=david@tethera.net \
    --cc=naveen.n.rao@linux.vnet.ibm.com \
    --cc=notmuch@notmuchmail.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).