From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <e@80x24.org>
X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on dcvr.yhbt.net
X-Spam-Level: 
X-Spam-ASN:  
X-Spam-Status: No, score=-4.0 required=3.0 tests=ALL_TRUSTED,BAYES_00
	shortcircuit=no autolearn=ham autolearn_force=no version=3.4.2
Received: from localhost (dcvr.yhbt.net [127.0.0.1])
	by dcvr.yhbt.net (Postfix) with ESMTP id 9A8731F8C8;
	Sat,  2 Oct 2021 11:39:15 +0000 (UTC)
Date: Sat, 2 Oct 2021 11:39:15 +0000
From: Eric Wong <e@80x24.org>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: meta@public-inbox.org
Subject: Re: Troubleshooting threads missing from /all/
Message-ID: <20211002113915.GA19320@dcvr>
References: <20211001130527.z7eivotlgqbgetzz@meerkat.local>
 <20211001201722.qvduabaqs7olrpc5@meerkat.local>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <20211001201722.qvduabaqs7olrpc5@meerkat.local>
List-Id: <meta.public-inbox.org>

Konstantin Ryabitsev <konstantin@linuxfoundation.org> wrote:
>   HTTP/1.1 300 Multiple Choices
> 
> However, this seems to happen for all unknown message-ids (e.g.
> lore.kernel.org/all/bogus@bogus), so probably entirely unrelated.

Yeah, unrelated, it's always returned 300 since I wanted to highlight
the fact there's many hosts out there which understand Message-IDs.

I just posted a few more patches, one which may help detect missing blobs:
https://public-inbox.org/meta/20211002111835.19220-5-e@80x24.org/

(I don't know if you log the output of extindex, I don't :x)

mid:87czop5j33.fsf@tynnyri.adurom.net
	a10c4087bee4dd10eee64903de80ca5c9c064db2
	ad29c5999a31edcbbed722b0d8299bf4f72bcae7

mid:d4405cdb-95ee-1dd9-6957-502269feb15e@leemhuis.info
	910d8e8beb3f5c692c4ba9522f6e22819cce69fb
	doesn't show up in l.k.o/all/ either...

So I wonder if there was a blob reachability problem during
indexing.

Btw, unlikely to matter, but are you using boost on either
regressions or linux-wireless?