From: Eric Wong <e@80x24.org>
To: Gonsolo <gonsolo@gmail.com>
Cc: meta@public-inbox.org
Subject: Re: Lei exception
Date: Thu, 14 Mar 2024 14:46:04 +0000 [thread overview]
Message-ID: <20240314144604.M774731@dcvr> (raw)
In-Reply-To: <CANL0fFSMQ1YL1a8PEpU39pYQ7d6vmmndughvJVue=SWNYNdqGQ@mail.gmail.com>
please keep meta@public-inbox.org in the Cc:
Gonsolo <gonsolo@gmail.com> wrote:
> > Which version of public-inbox is this? It looks like 1.9 based
> > on the line number[1].
>
> Package from Ubuntu/Debian.
>
> lei 1.9.0-1 (Ubuntu)
<snip>
> 936c275178dfc6908577487ce97d3a83c58c5449 PublicInbox/LeiSearch.pm
OK.
> > Any info you can share about the queries you use? (https, local
> > public-inbox clones).
>
> lei edit-search:
<snip>
> [lei "q"]
> include = https://lore.kernel.org/all/
> external = 1
> local = 1
> remote = 1
> threads = 1
OK, yeah. I seem to recall problems with http(s) externals
being racy and made more reliable with the use of OnDestroy
callbacks in public-inbox.git
> > I've seen it a few times in the past, but IIRC couldn't reliably
> > reproduce it and haven't seen it in a while. I'm always running
> > latest <https://80x24.org/public-inbox.git>, though, and that
> > has numerous reliability improvements over 1.9.
>
> Ok. Maybe I'm going to ping the Debian maintainer.
No, please don't ask Debian maintainers to package unreleased
versions. The non-lei feature: codesearch, is not ready to be
supported in a 2.0 release.
The only good news is 2.0 will probably be the last release
involving large data model additions/changes.
next prev parent reply other threads:[~2024-03-14 14:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-13 15:35 Lei exception Gonsolo
2024-03-13 19:20 ` Eric Wong
[not found] ` <CANL0fFSMQ1YL1a8PEpU39pYQ7d6vmmndughvJVue=SWNYNdqGQ@mail.gmail.com>
2024-03-14 14:46 ` Eric Wong [this message]
2024-03-15 17:36 ` Gonsolo
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=20240314144604.M774731@dcvr \
--to=e@80x24.org \
--cc=gonsolo@gmail.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).