unofficial mirror of meta@public-inbox.org
 help / color / mirror / Atom feed
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?
Date: Mon, 24 Jun 2019 17:33:19 +0000	[thread overview]
Message-ID: <20190624173319.3bb4t3zrieb4k5w2@dcvr> (raw)
In-Reply-To: <20190624163442.xhk6drl7ptnq7i5o@dcvr>

Eric Wong <e@80x24.org> wrote:
> "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?

How big are the gaps you're hitting?

> 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?

OK, I see this in my libc-alpha v2 mirror via -watch,
but not my v1 -watch mirrors.  Likely to affect -mda, too.
But the number gaps are small, however (1-2 messages), and.

  reply	other threads:[~2019-06-24 17:33 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-24 15:59 Q: Did you do something to message number recently? Eric W. Biederman
2019-06-24 16:34 ` Eric Wong
2019-06-24 17:33   ` Eric Wong [this message]
2019-06-24 22:56     ` Eric W. Biederman
2019-06-24 23:42       ` Eric Wong
2019-06-25 12:01         ` Eric W. Biederman
2019-06-25 17:51           ` Eric Wong
2019-06-24 23:38 ` [PATCH] msgmap: mid_insert: use plain "INSERT" to detect duplicates Eric Wong
2019-06-25  3:48   ` 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=20190624173319.3bb4t3zrieb4k5w2@dcvr \
    --to=e@80x24.org \
    --cc=ebiederm@xmission.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.
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).