From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: Kyle Meyer <kyle@kyleam.com>
Cc: meta@public-inbox.org
Subject: Re: empty /manifest.js.gz response as of 520be116
Date: Tue, 29 Jun 2021 09:02:26 -0400 [thread overview]
Message-ID: <20210629130226.pw364jhpfgi6ynx7@nitro.local> (raw)
In-Reply-To: <87fsx3128a.fsf@kyleam.com>
On Sun, Jun 27, 2021 at 04:28:37PM -0400, Kyle Meyer wrote:
> I recently upgraded a server from 08b649735 to 5860b498a and noticed
> that grok-pull didn't bring in any updates. It looks like what's going
> on is that the top-level /manifest.js.gz endpoint is now coming up
> empty.
BTW, I just added another hook feature to grokmirror that may be useful to
mirrors. This one is called when all new repos have finished cloning and will
hopefully help avoid situations where something like 3.git is done cloning
before any other epoch. It also helps keep things tidy and separate clone
events (that require public-inbox-init) from update events (that just need
public-inbox-index).
https://github.com/mricon/grokmirror/blob/master/grokmirror.conf#L142
It's not released yet, but hopefully 2.0.9 will be out after I do some more
testing.
-K
next prev parent reply other threads:[~2021-06-29 13:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-27 20:28 empty /manifest.js.gz response as of 520be116 Kyle Meyer
2021-06-28 21:59 ` [PATCH] www: fix manifest.js.gz for default publicInbox.grokManifest Eric Wong
2021-06-30 2:37 ` Kyle Meyer
2021-06-29 13:02 ` Konstantin Ryabitsev [this message]
2021-06-30 2:38 ` empty /manifest.js.gz response as of 520be116 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: 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=20210629130226.pw364jhpfgi6ynx7@nitro.local \
--to=konstantin@linuxfoundation.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).