user/dev discussion of public-inbox itself
 help / color / mirror / code / Atom feed
From: Kyle Meyer <kyle@kyleam.com>
To: meta@public-inbox.org
Subject: news.public-inbox.org misbehaving?
Date: Tue, 09 Jun 2020 22:13:55 +0000	[thread overview]
Message-ID: <87r1unyjj0.fsf@kyleam.com> (raw)

Checking inbox.comp.mail.public-inbox.meta today, I ran into some odd
behavior in my reader (Gnus).  While debugging that, I tried

  $ w3m -m nntp://news.public-inbox.org/inbox.comp.mail.public-inbox.meta

The tail of that buffer was

  4132 (06/06) Dmitry Alexandro Re: [Patch] Update 24-hour times to use two digits for the hour
  4133 (06/07) Eric Wong        [PATCH] index: v2: parallel by default

That didn't match up with what I saw at https://public-inbox.org/meta/:

  IMAP server notes, maybe JMAP?
   2020-06-09 11:34 UTC  - mbox.gz / Atom
  
  [PATCH] index: v2: parallel by default
   2020-06-07 20:02 UTC  - mbox.gz / Atom

inbox.comp.version-control.git also seems off.  After invoking w3m, I
landed on an empty

  Newsgroup: inbox.comp.version-control.git 399364-399413
  
  [399314-399363]

Following "[399314-399363]" displayed articles.  The last two were

  399326 (06/08) Denton Liu      Re: [PATCH] Recommend "git gc --prune=now" instead of "git prune"
  399327 (06/08) Simon Ser       Re: [PATCH v2] grep: add configuration variables for --heading

Again, that doesn't match what I see at https://public-inbox.org/git/,
which has a good number of messages from today (6/9).  And the empty
landing page/counts make me think that public-inbox-nntpd knows about
the articles that aren't being displayed.

Any ideas what might be going on?

             reply	other threads:[~2020-06-09 22:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-09 22:13 Kyle Meyer [this message]
2020-06-09 23:24 ` news.public-inbox.org misbehaving? Eric Wong
2020-06-11  0:57   ` [PATCH] nntpd+imapd: detect replaced over.sqlite3 Eric Wong
2020-06-11  1:54     ` Kyle Meyer

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: http://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=87r1unyjj0.fsf@kyleam.com \
    --to=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).