Naveen N. Rao wrote: > Naveen N. Rao wrote: >> David Bremner wrote: >>> David Bremner <david@tethera.net> writes: >>> >>>> "Naveen N. Rao" <naveen.n.rao@linux.vnet.ibm.com> writes: >>>> >>>>> >>>>> Were you able to look into this again? >>>>> Using a list of in-reply-to values sounds like a good option, though I >>>>> clearly have no idea about other consequences from that. If you have a >>>>> patch, I can help test that. >>>>> >>>> >>>> Sorry I haven't made any progress on this. Thanks for the reminder. >>>> >>>> d >>> >>> It's not much progress but I did manage to make a test case. >>> >>> id:20180730224555.26047-16-david@tethera.net >>> >>> 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. >> >> Thanks for continuing to look into this! >> >> The test is close to what I have -- the only difference in my case is >> that the Message-ID and References: fields match in the duplicate mail >> files, but just the In-reply-to headers differ (the gmane one has a >> meaningless/incorrect, re-written header). >> >> Interestingly though, I re-checked the thread I had the original problem >> with and notmuch seems to be able to cope with it better now. So, some >> other changes seem to have helped with my original problem. I will keep >> an eye out to see if any other threads cause problems (I do occasionally >> see astroid crash, but I haven't seen if it is due to this issue with >> notmuch or a different problem). >> >> [09/06 16:19:19 ~]$ notmuch --version >> notmuch 0.27 >> [09/06 16:19:20 ~]$ notmuch search --output=threads thread:00000000000c4d20 >> thread:00000000000c4d20 >> [09/06 16:19:22 ~]$ notmuch search --output=threads thread:00000000000c4d1e >> thread:00000000000c4d1e >> [09/06 16:19:26 ~]$ notmuch search --output=messages thread:00000000000c4d20 >> 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=messages thread:00000000000c4d1e >> id:CAKTCnzngahex_sL2raoHFuXqTxgVV7a57R9YmcT1TN-ROsFXnw@mail.gmail.com > > I've since moved away from Gmane and using public-inbox now and things > have been good all this while. Today, however, I hit this issue again. > I pull archives from lkml and linuxppc-dev and this thread is pulled in > 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@linux.vnet.ibm.com/T/#t > https://lore.kernel.org/lkml/cover.1561634177.git.naveen.n.rao@linux.vnet.ibm.com/T/#t > > [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 ppcdev sent) > thread:00000000000e364d Today 16:53 [8/11(31)] Naveen N. Rao| Steven Rostedt, Masami Hiramatsu; [PATCH v2 7/7] powerpc/kprobes: Allow probing on any ftrace address (imap inbox lkml new ppcdev replied sent unread) > thread:00000000000e3636 Today 15:29 [1/1(2)] Naveen N. Rao; [PATCH] powerpc/xmon: Fix disabling tracing while in xmon (imap inbox ppcdev) > thread:00000000000e357e Today 00:08 [1/4(12)] Naveen N. Rao| Michael Ellerman, Satheesh Rajendran, Steven Rostedt; [PATCH] recordmcount: Fix spurious mcount entries on powerpc (imap inbox lkml ppcdev) > [06/27 19:56:09 ~]$ > [06/27 19:56:14 ~]$ notmuch search --output=files -- thread:00000000000e364b > /home/naveen/news/news/ltcimap/Sent/cur/1561634919_0.18171.naverao1-tp,U=1356,FMD5=7f8c0283f16925caed8e632086b81b9c: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=files -- thread:00000000000e364d > /home/naveen/news/news/ltcimap/INBOX/new/1561645220_0.8024.naverao1-tp,U=151133,FMD5=7e33429f656f1e6e9d79b29c3f82c57e:2, > /home/naveen/news/news/ltcimap/INBOX/cur/1561643871_0.8024.naverao1-tp,U=151132,FMD5=7e33429f656f1e6e9d79b29c3f82c57e: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=1356,FMD5=7f8c0283f16925caed8e632086b81b9c: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=151129,FMD5=7e33429f656f1e6e9d79b29c3f82c57e: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=151128,FMD5=7e33429f656f1e6e9d79b29c3f82c57e: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=151127,FMD5=7e33429f656f1e6e9d79b29c3f82c57e: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=151126,FMD5=7e33429f656f1e6e9d79b29c3f82c57e: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=151125,FMD5=7e33429f656f1e6e9d79b29c3f82c57e: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=151124,FMD5=7e33429f656f1e6e9d79b29c3f82c57e: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=151123,FMD5=7e33429f656f1e6e9d79b29c3f82c57e: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=151122,FMD5=7e33429f656f1e6e9d79b29c3f82c57e: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 times, I was able to resolve this by using 'notmuch reindex' _twice_. The result quoted above was after I reindexed it once. But, the second re-index seems to have fixed this magically! - Naveen _______________________________________________ notmuch mailing list notmuch@notmuchmail.org https://notmuchmail.org/mailman/listinfo/notmuch