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-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 4E7101FB0A;
	Thu,  3 Dec 2020 20:19:45 +0000 (UTC)
Date: Thu, 3 Dec 2020 20:19:45 +0000
From: Eric Wong <e@80x24.org>
To: Kyle Meyer <kyle@kyleam.com>
Cc: meta@public-inbox.org
Subject: Re: missing messages in thread overview
Message-ID: <20201203201945.GA15810@dcvr>
References: <87360nlc44.fsf@kyleam.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <87360nlc44.fsf@kyleam.com>
List-Id: <meta.public-inbox.org>

Kyle Meyer <kyle@kyleam.com> wrote:
> <https://yhetil.org/debug-gap/>.

Thanks, I'm able to reproduce it.

<snip>

> Any ideas what might be going on here?

It seems like the presence of two ghosts in the histories fails
to get merged together; so it's order-dependency bug in
OverIdx.pm rethread seems to be exacerbating the condition (less
sure about rethread, though).

Basically, there should be only one distinct `tid' column
in the `over' table, but there's two tids and that's
causing over->get_thread to only see one tid or the other.

The top-level inbox view doesn't care about `tid' column, it
just fetches the most recent messages; so it's able to get
a complete view to render all the messages in the thread.

Will try to work on it more in a bit (struggling to decide
between starvation or possible COVID-19 exposure... :<)