user/dev discussion of public-inbox itself
 help / color / mirror / code / Atom feed
From: Eric Wong <e@80x24.org>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: meta@public-inbox.org
Subject: Re: Troubleshooting threads missing from /all/
Date: Thu, 7 Oct 2021 21:33:07 +0000	[thread overview]
Message-ID: <20211007213307.29376-0@dcvr> (raw)
In-Reply-To: <20211005180324.3miboond7ubth5v5@meerkat.local>

(resend, screwed up something with my MTA :x)

OK.  I tried reproducing the problem even with f28fdcd6d8d6
(content_hash: normalize whitespace before hashing addresses, 2021-10-02)
reverted, but haven't been able to...

So far I've found some gc and dedupe bugs, but something's still
eluding me.  And I also noticed and started fixing another bug
which may necessitate a full --reindex, anyways (at least for
non-ASCII subjects).

Konstantin Ryabitsev <konstantin@linuxfoundation.org> wrote:
> [publicinbox "regressions"]
>   address = regressions@lists.linux.dev
>   url = regressions
>   inboxdir = /srv/public-inbox/lore.kernel.org/regressions
>   indexlevel = full

Btw, "indexlevel = basic" ought to be sufficient if an inbox
is in extindex once bugs are ironed out.  full/medium is
of course helpful if messages are missing from extindex,
though...

  parent reply	other threads:[~2021-10-07 21:33 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-01 13:05 Troubleshooting threads missing from /all/ Konstantin Ryabitsev
2021-10-01 19:58 ` Eric Wong
2021-10-01 20:08   ` Konstantin Ryabitsev
2021-10-01 20:41     ` Eric Wong
2021-10-01 20:49       ` Konstantin Ryabitsev
2021-10-01 20:54         ` Eric Wong
2021-10-01 20:58           ` Konstantin Ryabitsev
2021-10-01 22:25             ` Eric Wong
2021-10-01 22:27               ` Eric Wong
2021-10-01 23:11               ` Konstantin Ryabitsev
2021-10-01 23:46                 ` Eric Wong
2021-10-02  0:02                   ` Eric Wong
2021-10-05  4:39                   ` Eric Wong
2021-10-05 18:03                     ` Konstantin Ryabitsev
2021-10-06 10:18                       ` Eric Wong
2021-10-07  8:36                         ` Eric Wong
2021-10-07 13:57                           ` Konstantin Ryabitsev
2021-10-07 21:36                             ` Eric Wong
2021-10-07 21:33                         ` Eric Wong
2021-10-07 21:33                       ` Eric Wong [this message]
2021-10-08 17:33                         ` Konstantin Ryabitsev
2021-10-08 21:34                           ` Eric Wong
2021-10-16  9:43                             ` Eric Wong
2021-10-17 18:04                               ` Konstantin Ryabitsev
2021-10-17 23:12                                 ` Eric Wong
2021-10-18  5:25                                   ` Eric Wong
2021-10-18 14:04                                     ` Konstantin Ryabitsev
2021-10-18 14:03                               ` Konstantin Ryabitsev
2021-10-24  0:03                                 ` Eric Wong
2021-10-26 21:11                                   ` Konstantin Ryabitsev
2021-10-29 10:18                                     ` release updates [was: Troubleshooting threads missing from /all/] Eric Wong
2021-10-01 20:17 ` Troubleshooting threads missing from /all/ Konstantin Ryabitsev
2021-10-02 11:39   ` 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=20211007213307.29376-0@dcvr \
    --to=e@80x24.org \
    --cc=konstantin@linuxfoundation.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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/public-inbox.git

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).