From: Josh Steadmon <steadmon@google.com>
To: meta@public-inbox.org
Subject: lei-up doesn't output replies to matching thread
Date: Thu, 11 Apr 2024 15:46:35 -0700 [thread overview]
Message-ID: <ZhhoSw7LIBIicRMv@google.com> (raw)
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!
next reply other threads:[~2024-04-11 22:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-11 22:46 Josh Steadmon [this message]
2024-04-12 2:07 ` lei-up doesn't output replies to matching thread Eric Wong
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://public-inbox.org/README
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZhhoSw7LIBIicRMv@google.com \
--to=steadmon@google.com \
--cc=meta@public-inbox.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).