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
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.
next prev parent 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 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
user/dev discussion of public-inbox itself
This inbox may be cloned and mirrored by anyone:
git clone --mirror https://public-inbox.org/meta
git clone --mirror http://czquwvybam4bgbro.onion/meta
git clone --mirror http://hjrcffqmbrq6wope.onion/meta
git clone --mirror http://ou63pmih66umazou.onion/meta
# If you have public-inbox 1.1+ installed, you may
# initialize and index your mirror using the following commands:
public-inbox-init -V1 meta meta/ https://public-inbox.org/meta \
meta@public-inbox.org
public-inbox-index meta
Example config snippet for mirrors.
Newsgroups are available over NNTP:
nntp://news.public-inbox.org/inbox.comp.mail.public-inbox.meta
nntp://ou63pmih66umazou.onion/inbox.comp.mail.public-inbox.meta
nntp://czquwvybam4bgbro.onion/inbox.comp.mail.public-inbox.meta
nntp://hjrcffqmbrq6wope.onion/inbox.comp.mail.public-inbox.meta
nntp://news.gmane.io/gmane.mail.public-inbox.general
note: .onion URLs require Tor: https://www.torproject.org/
code repositories for the project(s) associated with this inbox:
https://80x24.org/public-inbox.git
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git