From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on dcvr.yhbt.net X-Spam-Level: X-Spam-ASN: X-Spam-Status: No, score=-18.9 required=3.0 tests=AWL,BAYES_00,DKIMWL_WL_MED, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF, ENV_AND_HDR_SPF_MATCH,RCVD_IN_DNSWL_NONE,SPF_HELO_NONE,SPF_PASS, USER_IN_DEF_DKIM_WL,USER_IN_DEF_SPF_WL shortcircuit=no autolearn=ham autolearn_force=no version=3.4.6 Received: from mail-pf1-x42b.google.com (mail-pf1-x42b.google.com [IPv6:2607:f8b0:4864:20::42b]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by dcvr.yhbt.net (Postfix) with ESMTPS id D52C41F44D for ; Thu, 11 Apr 2024 22:46:42 +0000 (UTC) Authentication-Results: dcvr.yhbt.net; dkim=pass (2048-bit key; unprotected) header.d=google.com header.i=@google.com header.a=rsa-sha256 header.s=20230601 header.b=Q3aMgr13; dkim-atps=neutral Received: by mail-pf1-x42b.google.com with SMTP id d2e1a72fcca58-6ecf8ebff50so227816b3a.1 for ; Thu, 11 Apr 2024 15:46:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20230601; t=1712875601; x=1713480401; darn=public-inbox.org; h=content-disposition:mime-version:message-id:subject:to:from:date :from:to:cc:subject:date:message-id:reply-to; bh=a0sBneVmed6hhyI4oowX3kWtPAo9ECt63PW2PaWXBTM=; b=Q3aMgr137cIL6mdngOQtHQkvBKQgtfay7qjiDITwIm86fnFxRTpGDuX1ZGv6P6k5To QG+7cM+fTcOOCnubdiJVQ6y42b5H/ZsMWdgw1qf+/+qzdNDW8uxUKv0WruMSodUZpaiE 81Vj6lVq5tB5rxitcFLcM9H7BGqlq38krQxjMk/jkZ6M9qjMRvPXn0+tMI0Qf0JMUL6S uWevhPhvv7pY+6FWXKsgq59GOOzMCx6pun3aLielAmwJj0C5UzJPuIHOptDKXK+xob3w N1gNo9V5GYYbZQVYByAo9Sb8eIPh41eD5HqFumCHoZcZUGRLm0VhJrZKU7ONYcrBjZM8 AA2w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1712875601; x=1713480401; h=content-disposition:mime-version:message-id:subject:to:from:date :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=a0sBneVmed6hhyI4oowX3kWtPAo9ECt63PW2PaWXBTM=; b=IAgKw842kHo+87FZXCJo++0kP9RYC6ERPRc5/yjkGKLgn8ySPIBnB3tj4E+/T2eeTz 9AIl1kTLuGYiA5/+8aKxbZIWPWt6vdBOBUhmOm0YRNarbRBGhA4gDYbhCK3OBRjco4ue UeIEavMp6Y/mp9YZzf83Y+dBEv6fhmCv2OnYQnhtKfhLO0CSPJIWhbqcARx3+0y7JzGg QOBW5yI80m9uoWUZoYJ3Z6Hmy/NBXKwDmBdb18ud8L2OvjqW9kiFfTGpuFSItnt9ZSaf M9oDx67O85TF2DwrsAhB8iaN3HQMJuv+/Oj5IcXzpbaDKVOPJmfzqpZtYUdDpQJqdll4 HIXg== X-Gm-Message-State: AOJu0Ywx+TUVO8ZAmehwiMI4jQ0Hp0KBj/RBwWV9nc0VpFPDOZH6mPFv wDLUuHqaRmEpNM6Itt+CDkvfBlcUKjhdK3ARj1b3iOxYAASpGdsIkw41zYngnJ8TsQhjIsZd6/h Kbw== X-Google-Smtp-Source: AGHT+IFFT5s6N4ORegkoMgrDGxpkBsLyWkkhB9U5MFn2/KwyUHkQwHeXqD2iIbGhbVTrpsRqzvi24g== X-Received: by 2002:a05:6a00:3904:b0:6ed:e1c:1038 with SMTP id fh4-20020a056a00390400b006ed0e1c1038mr1225383pfb.7.1712875600632; Thu, 11 Apr 2024 15:46:40 -0700 (PDT) Received: from google.com ([2620:15c:2d3:204:5d8a:5a85:8673:4f76]) by smtp.gmail.com with ESMTPSA id u32-20020a056a0009a000b006eaf43bbcb5sm1672532pfg.114.2024.04.11.15.46.39 for (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 11 Apr 2024 15:46:40 -0700 (PDT) Date: Thu, 11 Apr 2024 15:46:35 -0700 From: Josh Steadmon To: meta@public-inbox.org Subject: lei-up doesn't output replies to matching thread Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline List-Id: Hello again, I'm having trouble where `lei up --all` is not outputting threaded replies, despite the fact that the saved search requests them. I noticed the problem on this Git thread: https://lore.kernel.org/git/520da361-1b80-4ba3-87b2-86d6fdfc18b5@web.de/ My saved search is as follows: { "output": "maildir:/usr/local/google/home/steadmon/.mail/lei-git-unit-tests", "q": ["(dfn:t/unit-tests OR s:unit OR ((nq:bug OR nq:regression) AND nq:unit)) AND rt:2.weeks.ago.."], "external": "1", "local": "1", "remote": "1", "threads": "1" } Lei is aware of the replies, because I can see them with lei-q if I copy the query from the saved search: $ lei q -t "(dfn:t/unit-tests OR s:unit OR ((nq:bug OR nq:regression) AND nq:unit)) AND rt:2.weeks.ago.." \ | grep "t-prio-queue: simplify using compound literals" \ | wc -l 11 In my output maildir, I only have the initial message that started the thread: $ cd ~/.mail/lei-git-unit-tests $ grep -Rl "Subject:.*t-prio-queue: simplify using compound literals" \ | wc -l 1 And lei-up does not seem to see those matches: $ lei up ~/.mail/lei-git-unit-tests # /usr/local/google/home/steadmon/.local/share/lei/store 10/10 # 0 written to /usr/local/google/home/steadmon/.mail/lei-git-unit-tests/ (10 matches) I have not noticed the problem for other threads, but I am not 100% sure that it's limited to just this one, either. If you have any advice for further debugging, I'd appreciate the help. Thanks!