From: Xu Wang Date: Thu, 24 Sep 2015 00:55:32 +0000 (+2000) Subject: Re: Possible some threads are not complete due to bug? X-Git-Url: http://git.tremily.us/?a=commitdiff_plain;h=6895408b19f754ff54c15e93d33d535ea88fddb4;p=notmuch-archives.git Re: Possible some threads are not complete due to bug? --- diff --git a/2c/9eb2f1c0f03cfe66010864e57cde96513e1c46 b/2c/9eb2f1c0f03cfe66010864e57cde96513e1c46 new file mode 100644 index 000000000..a9f92ccb7 --- /dev/null +++ b/2c/9eb2f1c0f03cfe66010864e57cde96513e1c46 @@ -0,0 +1,117 @@ +Return-Path: +X-Original-To: notmuch@notmuchmail.org +Delivered-To: notmuch@notmuchmail.org +Received: from localhost (localhost [127.0.0.1]) + by arlo.cworth.org (Postfix) with ESMTP id D59846DE0FB1 + for ; Wed, 23 Sep 2015 17:55:38 -0700 (PDT) +X-Virus-Scanned: Debian amavisd-new at cworth.org +X-Spam-Flag: NO +X-Spam-Score: -0.173 +X-Spam-Level: +X-Spam-Status: No, score=-0.173 tagged_above=-999 required=5 + tests=[AWL=-0.347, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, + DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, + FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, + RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_SBL=0.644, + URIBL_SBL_A=0.1] 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 aULF7_Qbj_54 for ; + Wed, 23 Sep 2015 17:55:36 -0700 (PDT) +Received: from mail-ob0-f179.google.com (mail-ob0-f179.google.com + [209.85.214.179]) + by arlo.cworth.org (Postfix) with ESMTPS id AD8E96DE0C66 + for ; Wed, 23 Sep 2015 17:55:36 -0700 (PDT) +Received: by obbzf10 with SMTP id zf10so46968985obb.2 + for ; Wed, 23 Sep 2015 17:55:33 -0700 (PDT) +DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; + h=mime-version:in-reply-to:references:date:message-id:subject:from:to + :cc:content-type; + bh=KUpNltgSH28MCXziv5DJqCaJ58irIqvzzH7SS0B0ZH0=; + b=Digupic0/atqLeOkFpa4P6bnmrHoSVLzff5su9nTA+UZPd2QyIT9MameLOK7ojizk5 + 3RPrMlb849HonLGPGyQmKs6VRL7WmLlhax/ay3DJeIbby0p2Jq5qoAs0DQLGPx/1CBpH + e6U/czoKDhWpGaG1hMGGjWYRNSP78fIplVjJGOAL6auLAitLXvjsKrLxZHpDbtnSRmcl + n+aXkIFupcjq9k0UfNQiJOGsdlGnp8tw5iq2zfYlXG2Uhx1JeZq4N56ulemRhOyzaBqI + ZTgUqRwD8rEVafLTLsPzyc6MuxSpGa+L4EV0BqsisNDObwxP9slwXpR1YKruDhkLIOp0 + zfQQ== +MIME-Version: 1.0 +X-Received: by 10.60.144.197 with SMTP id so5mr3923240oeb.29.1443056132540; + Wed, 23 Sep 2015 17:55:32 -0700 (PDT) +Received: by 10.202.212.204 with HTTP; Wed, 23 Sep 2015 17:55:32 -0700 (PDT) +In-Reply-To: <87zj0c3gei.fsf@zancas.localnet> +References: + + <87fv2a4ctt.fsf@zancas.localnet> + + <87zj0c3gei.fsf@zancas.localnet> +Date: Wed, 23 Sep 2015 20:55:32 -0400 +Message-ID: + +Subject: Re: Possible some threads are not complete due to bug? +From: Xu Wang +To: David Bremner +Content-Type: text/plain; charset=UTF-8 +Cc: notmuch@notmuchmail.org +X-BeenThere: notmuch@notmuchmail.org +X-Mailman-Version: 2.1.18 +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, 24 Sep 2015 00:55:38 -0000 + +On Wed, Sep 23, 2015 at 6:44 PM, David Bremner wrote: +> Xu Wang writes: +> +>> Because when I do a notmuch search for that message by message ID with +>> --output=threads, it gives a different thread ID. +>> +>>> Isn't that what your first command tells you? +>> Well yes, but I wanted to confirm that that is indeed the reason. I +>> have heard in someone saying that debugging is process of confirming +>> things that should be true. +> +> I'm still confused. It sounds like you gave the same command twice and +> got different answers. Can you maybe show the complete sequence of +> commands and output (assuming it's not too large)? + +Dear David, thank you for your kind persistence. I apologize for the +lack of clarity in my writing. Below is the full sequence of commands +(I just subsitute MYMSGID and MYMSGIDREPLY for two message IDs) as +well as my thought process. + +$ notmuch search --output=threads "id:MYMSGID" +thread:000000000000a125 +$ notmuch search --output=messages "thread:000000000000a125" +id:MYMSGID +$ +# I know that MYMSGIDREPLY did respond to that message. I have it in +my mutt mailbox and it shows the down-right arrow signifying this. I +inspect the headers and there is indeed a header in MYMSGIDREPLY that +says "In-Reply-To: ". I then do... +$ notmuch search --output=threads "id:MYMSGIDREPLY" +thread:000000000000c125 +$ notmuch search --output=messages "thread:000000000000c125" +id:MYMSGIDREPLY +$ + +# What I expected (and did not get) was the following output: +$ notmuch search --output=threads "id:MYMSGID" +thread:000000000000a125 +$ notmuch search --output=messages "thread:000000000000a125" +id:MYMSGID +id:MYMSGIDREPLY +$ + +# after regenerating the notmuch database, I did indeed get the output +that I expected. + +Kind regards, + +Xu