From: Jacob Keller <jacob.e.keller@intel.com>
To: Eric Wong <e@80x24.org>
Cc: <meta@public-inbox.org>
Subject: Re: search by whole thread?
Date: Wed, 12 Apr 2023 11:29:30 -0700 [thread overview]
Message-ID: <6d409755-84bf-b88e-4f5b-7b13abe216b0@intel.com> (raw)
In-Reply-To: <20230412000654.M9394@dcvr>
On 4/11/2023 5:06 PM, Eric Wong wrote:
> Jacob Keller <jacob.e.keller@intel.com> wrote:
>> Hi,
>>
>> I'm wondering if there is a way to search a list by the entire thread?
>
> Not yet...
>
>> For example, I want to find all threads which have at least one message
>> with dfn:<some path> and which have no messages containing the text
>> "Reviewed-by".
>>
>> This would for example let me search an open source archive for threads
>> (patch series for example) which have not received any reviewed-by reply.
>
> Yes, that's something I've wanted, too...
>
>> The current search function available through the HTML website doesn't
>> seem to have a "by thread" function. I also haven't been able to find
>> any option similar to this in the email client I typically use for
>> interacting with the lists (Thunderbird).
>
> I think the reason it's rare in MUAs is that it's potentially
> very expensive. But I think the `thread:{subquery}' feature
> from notmuch I discussed with Konstantin the other week[1] can
> do what you want it to do.
>
> Keep in mind, notmuch-search-terms(7) states:
>
> The performance of such queries can vary wildly.
>
> And that's for a private client tool for a single user.
>
> For a public-facing web UI, we'll need proper timeouts (likely
> via RLIMIT_CPU + SIGXCPU) in an external process and a C++ build
> against libxapian. AFAIK, custom query parsers aren't possible
> in Xapian's high-level language bindings; fortunately I can
> legally reuse GPL-3+ C++ code from notmuch \o/
>
> The external process will probably be similar to
> `git cat-file --batch-command' though it can use SOCK_SEQPACKET
> for requests and pipes for large responses.
>
>> Perhaps this is something that I could implement locally from the clone
>> of the archive, but I am not quite sure how to go about it.. It seems
>> like something that should be reasonably straight forward given the way
>> that public inbox already tracks threads. Any suggestions on how to get
>> something like this would be appreciated.
>
> Are you able to confirm notmuch `thread:{subquery}' is what
> you're after?
Ah. I tried searching but didn't hit upon not much. To be honest, I bet
just directly using notmuch and having it subscribe to the messages from
the public inbox would be sufficient for my purposes :D
I'll explore this and see, but it does sound like the thread:{subquery}
is basically what I want.
>
> I plan on implementing it with proper timeouts for untrusted
> clients within the next few weeks/months; assuming some other
> stuff works out and I still have Internet + power.
>
>
> [1] https://public-inbox.org/meta/20230328194549.M808175@dcvr/
next prev parent reply other threads:[~2023-04-12 18:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-11 22:59 search by whole thread? Jacob Keller
2023-04-12 0:06 ` Eric Wong
2023-04-12 18:29 ` Jacob Keller [this message]
2023-04-12 18:49 ` Konstantin Ryabitsev
2023-04-12 20:17 ` Eric Wong
2023-04-12 21:01 ` Jacob Keller
2023-04-12 21:21 ` 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=6d409755-84bf-b88e-4f5b-7b13abe216b0@intel.com \
--to=jacob.e.keller@intel.com \
--cc=e@80x24.org \
--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).