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 7C5F06DE12E5 for ; Thu, 27 Jun 2019 08:28:20 -0700 (PDT) X-Virus-Scanned: Debian amavisd-new at cworth.org X-Spam-Flag: NO X-Spam-Score: -0.699 X-Spam-Level: X-Spam-Status: No, score=-0.699 tagged_above=-999 required=5 tests=[KHOP_DYNAMIC=0.001, RCVD_IN_DNSWL_LOW=-0.7] 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 OOwWC8DmeSZZ for ; Thu, 27 Jun 2019 08:28:19 -0700 (PDT) X-Greylist: delayed 2101 seconds by postgrey-1.36 at arlo; Thu, 27 Jun 2019 08:28:19 PDT Received: from mx0a-001b2d01.pphosted.com (mx0a-001b2d01.pphosted.com [148.163.156.1]) by arlo.cworth.org (Postfix) with ESMTPS id 342876DE0F17 for ; Thu, 27 Jun 2019 08:28:19 -0700 (PDT) Received: from pps.filterd (m0098393.ppops.net [127.0.0.1]) by mx0a-001b2d01.pphosted.com (8.16.0.27/8.16.0.27) with SMTP id x5REiTam137224 for ; Thu, 27 Jun 2019 10:53:17 -0400 Received: from e06smtp07.uk.ibm.com (e06smtp07.uk.ibm.com [195.75.94.103]) by mx0a-001b2d01.pphosted.com with ESMTP id 2tcx4xq3dn-1 (version=TLSv1.2 cipher=AES256-GCM-SHA384 bits=256 verify=NOT) for ; Thu, 27 Jun 2019 10:53:16 -0400 Received: from localhost by e06smtp07.uk.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for from ; Thu, 27 Jun 2019 15:53:14 +0100 Received: from b06avi18878370.portsmouth.uk.ibm.com (9.149.26.194) by e06smtp07.uk.ibm.com (192.168.101.137) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted; (version=TLSv1/SSLv3 cipher=AES256-GCM-SHA384 bits=256/256) Thu, 27 Jun 2019 15:53:12 +0100 Received: from d06av21.portsmouth.uk.ibm.com (d06av21.portsmouth.uk.ibm.com [9.149.105.232]) by b06avi18878370.portsmouth.uk.ibm.com (8.14.9/8.14.9/NCO v10.0) with ESMTP id x5RErBqs23855462 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Thu, 27 Jun 2019 14:53:11 GMT Received: from d06av21.portsmouth.uk.ibm.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id C3A5952054; Thu, 27 Jun 2019 14:53:11 +0000 (GMT) Received: from localhost (unknown [9.199.59.170]) by d06av21.portsmouth.uk.ibm.com (Postfix) with ESMTP id 611F05204E; Thu, 27 Jun 2019 14:53:11 +0000 (GMT) Date: Thu, 27 Jun 2019 20:23:10 +0530 From: "Naveen N. Rao" Subject: Re: 'notmuch search thread:<>' lists multiple threads To: David Bremner , notmuch@notmuchmail.org References: <1523007700.l8xm6nm6af.naveen@linux.ibm.com> <87sh86v1oc.fsf@tethera.net> <878t9wvbmu.fsf@tethera.net> <1524045467.a0aq8zermb.naveen@linux.ibm.com> <87r2n8m5ky.fsf@tethera.net> <1530181883.fliclpetue.naveen@linux.ibm.com> <87zhzccrwg.fsf@tethera.net> <87d0u0nhiz.fsf@unb.ca> <1536230687.efahvzbzyt.naveen@linux.ibm.com> <1561646623.zzt85d10l1.naveen@linux.ibm.com> In-Reply-To: <1561646623.zzt85d10l1.naveen@linux.ibm.com> User-Agent: astroid/0.14.0 (https://github.com/astroidmail/astroid) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: quoted-printable X-TM-AS-GCONF: 00 x-cbid: 19062714-0028-0000-0000-0000037E4092 X-IBM-AV-DETECTION: SAVI=unused REMOTE=unused XFE=unused x-cbparentid: 19062714-0029-0000-0000-0000243E6B38 Message-Id: <1561647093.v3y2anav5a.naveen@linux.ibm.com> X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2019-06-27_09:, , signatures=0 X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1015 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1810050000 definitions=main-1906270172 X-Mailman-Approved-At: Thu, 27 Jun 2019 10:15:48 -0700 X-BeenThere: notmuch@notmuchmail.org X-Mailman-Version: 2.1.29 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: Thu, 27 Jun 2019 15:28:20 -0000 Naveen N. Rao wrote: > Naveen N. Rao wrote: >> David Bremner wrote: >>> David Bremner writes: >>>=20 >>>> "Naveen N. Rao" writes: >>>> >>>>> >>>>> Were you able to look into this again? >>>>> Using a list of in-reply-to values sounds like a good option, though = I=20 >>>>> clearly have no idea about other consequences from that. If you have = a=20 >>>>> patch, I can help test that. >>>>> >>>> >>>> Sorry I haven't made any progress on this. Thanks for the reminder. >>>> >>>> d >>>=20 >>> It's not much progress but I did manage to make a test case. >>>=20 >>> id:20180730224555.26047-16-david@tethera.net >>>=20 >>> As it says in the commit message, its not 100% clear this is your >>> problem, but it is a bug, and hopefully fixing it will help your issue. >>=20 >> Thanks for continuing to look into this! >>=20 >> The test is close to what I have -- the only difference in my case is=20 >> that the Message-ID and References: fields match in the duplicate mail=20 >> files, but just the In-reply-to headers differ (the gmane one has a=20 >> meaningless/incorrect, re-written header). >>=20 >> Interestingly though, I re-checked the thread I had the original problem= =20 >> with and notmuch seems to be able to cope with it better now. So, some=20 >> other changes seem to have helped with my original problem. I will keep=20 >> an eye out to see if any other threads cause problems (I do occasionally= =20 >> see astroid crash, but I haven't seen if it is due to this issue with=20 >> notmuch or a different problem). >>=20 >> [09/06 16:19:19 ~]$ notmuch --version >> notmuch 0.27 >> [09/06 16:19:20 ~]$ notmuch search --output=3Dthreads thread:000000000= 00c4d20 >> thread:00000000000c4d20 >> [09/06 16:19:22 ~]$ notmuch search --output=3Dthreads thread:000000000= 00c4d1e >> thread:00000000000c4d1e >> [09/06 16:19:26 ~]$ notmuch search --output=3Dmessages thread:00000000= 000c4d20 >> id:20180813154910.lzrkd2ivdorge3ro@arbab-laptop.localdomain >> id:CAKTCnzngahex_sL2raoHFuXqTxgVV7a57R9YmcT1TN-ROsFXnw@mail.gmail.com >> id:CAOSf1CFy0im+H368Krr2QVteAumq58CRF_Kfatyv7wvj1n4AGw@mail.gmail.com >> id:20180405071500.22320-4-bsingharora@gmail.com >> id:20180405071500.22320-3-bsingharora@gmail.com >> id:20180405071500.22320-2-bsingharora@gmail.com >> id:20180405071500.22320-1-bsingharora@gmail.com >> [09/06 16:19:35 ~]$ notmuch search --output=3Dmessages thread:00000000= 000c4d1e >> id:CAKTCnzngahex_sL2raoHFuXqTxgVV7a57R9YmcT1TN-ROsFXnw@mail.gmail.com >=20 > I've since moved away from Gmane and using public-inbox now and things=20 > have been good all this while. Today, however, I hit this issue again. =20 > I pull archives from lkml and linuxppc-dev and this thread is pulled in=20 > from both those places, as well as from my local IMAP sent folder: > https://lore.kernel.org/linuxppc-dev/cover.1561634177.git.naveen.n.rao@li= nux.vnet.ibm.com/T/#t > https://lore.kernel.org/lkml/cover.1561634177.git.naveen.n.rao@linux.vnet= .ibm.com/T/#t >=20 > [06/27 19:56:07 ~]$ notmuch search -- tag:ppcdev and date:today and from:= naveen > thread:00000000000e364b Today 16:57 [1/1(3)] Naveen N. Rao; [PATCH v2 2/= 7] x86/ftrace: Fix use of flags in ftrace_replace_code() (imap inbox lkml p= pcdev sent) > thread:00000000000e364d Today 16:53 [8/11(31)] Naveen N. Rao| Steven Ros= tedt, Masami Hiramatsu; [PATCH v2 7/7] powerpc/kprobes: Allow probing on an= y ftrace address (imap inbox lkml new ppcdev replied sent unread) > thread:00000000000e3636 Today 15:29 [1/1(2)] Naveen N. Rao; [PATCH] powe= rpc/xmon: Fix disabling tracing while in xmon (imap inbox ppcdev) > thread:00000000000e357e Today 00:08 [1/4(12)] Naveen N. Rao| Michael Ell= erman, Satheesh Rajendran, Steven Rostedt; [PATCH] recordmcount: Fix spurio= us mcount entries on powerpc (imap inbox lkml ppcdev) > [06/27 19:56:09 ~]$=20 > [06/27 19:56:14 ~]$ notmuch search --output=3Dfiles -- thread:00000000000= e364b > /home/naveen/news/news/ltcimap/Sent/cur/1561634919_0.18171.naverao1-tp,U= =3D1356,FMD5=3D7f8c0283f16925caed8e632086b81b9c:2,S > /home/naveen/news/news/lore.kernel.org/linuxppc-dev/0/223040 > /home/naveen/news/news/lore.kernel.org/lkml/7/120234 > [06/27 19:56:34 ~]$ notmuch search --output=3Dfiles -- thread:00000000000= e364d > /home/naveen/news/news/ltcimap/INBOX/new/1561645220_0.8024.naverao1-tp,U= =3D151133,FMD5=3D7e33429f656f1e6e9d79b29c3f82c57e:2, > /home/naveen/news/news/ltcimap/INBOX/cur/1561643871_0.8024.naverao1-tp,U= =3D151132,FMD5=3D7e33429f656f1e6e9d79b29c3f82c57e:2,S > /home/naveen/news/news/lore.kernel.org/linuxppc-dev/0/223042 > /home/naveen/news/news/lore.kernel.org/lkml/7/120325 > /home/naveen/news/news/ltcimap/Sent/cur/1561634919_0.18171.naverao1-tp,U= =3D1356,FMD5=3D7f8c0283f16925caed8e632086b81b9c:2,S > /home/naveen/news/news/lore.kernel.org/linuxppc-dev/0/223040 > /home/naveen/news/news/lore.kernel.org/lkml/7/120234 > /home/naveen/news/news/ltcimap/INBOX/cur/1561634683_0.18171.naverao1-tp,U= =3D151129,FMD5=3D7e33429f656f1e6e9d79b29c3f82c57e:2,S > /home/naveen/news/news/lore.kernel.org/linuxppc-dev/0/223038 > /home/naveen/news/news/lore.kernel.org/lkml/7/120225 > /home/naveen/news/news/ltcimap/INBOX/cur/1561634682_6.18171.naverao1-tp,U= =3D151128,FMD5=3D7e33429f656f1e6e9d79b29c3f82c57e:2,S > /home/naveen/news/news/lore.kernel.org/linuxppc-dev/0/223039 > /home/naveen/news/news/lore.kernel.org/lkml/7/120224 > /home/naveen/news/news/ltcimap/INBOX/cur/1561634682_5.18171.naverao1-tp,U= =3D151127,FMD5=3D7e33429f656f1e6e9d79b29c3f82c57e:2,S > /home/naveen/news/news/lore.kernel.org/linuxppc-dev/0/223037 > /home/naveen/news/news/lore.kernel.org/lkml/7/120223 > /home/naveen/news/news/ltcimap/INBOX/cur/1561634682_0.18171.naverao1-tp,U= =3D151126,FMD5=3D7e33429f656f1e6e9d79b29c3f82c57e:2,S > /home/naveen/news/news/lore.kernel.org/linuxppc-dev/0/223036 > /home/naveen/news/news/lore.kernel.org/lkml/7/120222 > /home/naveen/news/news/ltcimap/INBOX/cur/1561634682_4.18171.naverao1-tp,U= =3D151125,FMD5=3D7e33429f656f1e6e9d79b29c3f82c57e:2,S > /home/naveen/news/news/lore.kernel.org/linuxppc-dev/0/223035 > /home/naveen/news/news/lore.kernel.org/lkml/7/120221 > /home/naveen/news/news/ltcimap/INBOX/cur/1561634682_1.18171.naverao1-tp,U= =3D151124,FMD5=3D7e33429f656f1e6e9d79b29c3f82c57e:2,RS > /home/naveen/news/news/lore.kernel.org/linuxppc-dev/0/223034 > /home/naveen/news/news/lore.kernel.org/lkml/7/120220 > /home/naveen/news/news/ltcimap/INBOX/cur/1561634682_3.18171.naverao1-tp,U= =3D151123,FMD5=3D7e33429f656f1e6e9d79b29c3f82c57e:2,S > /home/naveen/news/news/lore.kernel.org/linuxppc-dev/0/223033 > /home/naveen/news/news/lore.kernel.org/lkml/7/120219 > /home/naveen/news/news/ltcimap/INBOX/cur/1561634682_2.18171.naverao1-tp,U= =3D151122,FMD5=3D7e33429f656f1e6e9d79b29c3f82c57e:2,S > /home/naveen/news/news/lore.kernel.org/linuxppc-dev/0/223031 > /home/naveen/news/news/lore.kernel.org/lkml/7/120218 After being unable to open this thread in astroid email client a few=20 times, I was able to resolve this by using 'notmuch reindex' _twice_. =20 The result quoted above was after I reindexed it once. But, the second=20 re-index seems to have fixed this magically! - Naveen =