user/dev discussion of public-inbox itself
 help / color / mirror / code / Atom feed
From: Eric Wong <e@80x24.org>
To: Kyle Meyer <kyle@kyleam.com>
Cc: meta@public-inbox.org
Subject: Re: missing messages in thread overview
Date: Thu, 3 Dec 2020 20:19:45 +0000	[thread overview]
Message-ID: <20201203201945.GA15810@dcvr> (raw)
In-Reply-To: <87360nlc44.fsf@kyleam.com>

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

  reply	other threads:[~2020-12-03 20:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-03  4:59 missing messages in thread overview Kyle Meyer
2020-12-03 20:19 ` Eric Wong [this message]
2020-12-04  2:12   ` [WIP] over: ensure old, merged {tid} is really gone Eric Wong
2020-12-04  3:35     ` Kyle Meyer
2020-12-04 12:09       ` [PATCH] " 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=20201203201945.GA15810@dcvr \
    --to=e@80x24.org \
    --cc=kyle@kyleam.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.
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).