From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on dcvr.yhbt.net X-Spam-Level: X-Spam-ASN: AS3215 2.6.0.0/16 X-Spam-Status: No, score=-3.8 required=3.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_HI, SPF_HELO_NONE,SPF_PASS,T_SCC_BODY_TEXT_LINE shortcircuit=no autolearn=ham autolearn_force=no version=3.4.2 Received: from dfw.source.kernel.org (dfw.source.kernel.org [IPv6:2604:1380:4641:c500::1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by dcvr.yhbt.net (Postfix) with ESMTPS id EB0CD1F727 for ; Wed, 29 Jun 2022 16:15:26 +0000 (UTC) Authentication-Results: dcvr.yhbt.net; dkim=pass (2048-bit key; unprotected) header.d=kernel.org header.i=@kernel.org header.b="mr4ljdmB"; dkim-atps=neutral Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by dfw.source.kernel.org (Postfix) with ESMTPS id C9EB361BB8 for ; Wed, 29 Jun 2022 16:15:25 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 32589C341C8 for ; Wed, 29 Jun 2022 16:15:25 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1656519325; bh=PDe2IsGjSg+DdQScbZmlmKR0u9JVFWnTk4NPqmoTig8=; h=From:Date:Subject:To:From; b=mr4ljdmBIXC5UMRjDOOLUO8SUzGDMoEL4gSwiSoqgUrSQqj/1HSRklkjgdOgVYXTt Tt+RMno/jlOXAX8ODrqoSYglRg8X4vtfr02l5qpp4Ah5aaYCOqD18KTYKEyziNseHa 06ewSgHlAVgZ79mACdPW2Awa35Vdkc2on5Hnxrz7t7JGczCGVlLEag+6hv14yDK1WF FPSymiQs6TfqTvgquSG5L9QwUH4HySsemAwHfAesbIsjCNdLIdavjC1bL7fvJO+PvA 65HB2vhJZlrWD1KOyIl/hABPrkW2iSskDqvFslKhKv0qFa0sUv4zEzcbDwV9FkNiJ9 cnseLPUleqvSQ== Received: by mail-vk1-f174.google.com with SMTP id r1so6611870vke.8 for ; Wed, 29 Jun 2022 09:15:25 -0700 (PDT) X-Gm-Message-State: AJIora+q6iIPxBrm2vwE2UgdFnIfmGg/yHVoT/UPY07bw76RxNj6b4Ae 8p3ss+0kw5V5knNds8B1KbVrnsSof9eEndXT9Q== X-Google-Smtp-Source: AGRyM1tmW0QP+DumNIUuhmaE7pFieLW2XgBRl0Z/PuGmZSAlfORs67qi+yHuFHTwItWHfLSFXyeZo5bazKHpzJXHbVY= X-Received: by 2002:a1f:2bd5:0:b0:370:23aa:ead7 with SMTP id r204-20020a1f2bd5000000b0037023aaead7mr4888250vkr.26.1656519324163; Wed, 29 Jun 2022 09:15:24 -0700 (PDT) MIME-Version: 1.0 From: Rob Herring Date: Wed, 29 Jun 2022 10:15:12 -0600 X-Gmail-Original-Message-ID: Message-ID: Subject: lei missing mails To: meta@public-inbox.org Content-Type: text/plain; charset="UTF-8" List-Id: Hi, I'm using lei with lore where I have 2 queries which overlap. Really, one is a subset of the other. On those overlapping threads, I'm finding that sometimes new messages are written to one mailbox and not the other. (At least sometimes, the messages may be missing from all mailboxes sometimes too. I'm not certain.) Using --remote-fudge-time to force refetching seems to get the missing mails. I haven't found anything strange in timestamps of the missing mails, but otherwise am not sure how to debug this further. The queries are retrieving full threads and the missing mails are in the threads, but not direct matches to the queries. I realize that's not a lot of detail to go on. Suggestions on debugging this further? It might be helpful if lei could print out message-ids of messages written to mailboxes. Rob