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 152171F461;
	Mon, 24 Jun 2019 16:34:43 +0000 (UTC)
Date: Mon, 24 Jun 2019 16:34:42 +0000
From: Eric Wong <e@80x24.org>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: meta@public-inbox.org
Subject: Re: Q: Did you do something to message number recently?
Message-ID: <20190624163442.xhk6drl7ptnq7i5o@dcvr>
References: <878strvusz.fsf@xmission.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <878strvusz.fsf@xmission.com>
List-Id: <meta.public-inbox.org>

"Eric W. Biederman" <ebiederm@xmission.com> wrote:
> 
> Eric,
> 
> I am just starting to dig into this, I just noticed that I have several
> inboxes that are seeing huge skips in message numbers assigned in
> msgmap.  Do you have any idea why this would be?

I've hit this in the past using the altid stuff to keep NNTP
article numbers in check.

There's a lot of changes w.r.t. progress reporting, no-op
speedups,

> If not I will dig in and figure this out.  I just figured I would ask
> in case you have any handy canidates.

Are you hitting this with "git fetch && public-inbox-index" or
-watch/-mda?

> I thought I had a regression test in public-inbox to catch this.

Me too.