unofficial mirror of meta@public-inbox.org
 help / color / mirror / Atom feed
From: Kyle Meyer <kyle@kyleam.com>
To: meta@public-inbox.org
Subject: empty /manifest.js.gz response as of 520be116
Date: Sun, 27 Jun 2021 16:28:37 -0400	[thread overview]
Message-ID: <87fsx3128a.fsf@kyleam.com> (raw)

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.

A minimal example on 5860b498a:

  $ git clone --mirror https://try.public-inbox.org/test test
  $ export PI_CONFIG="$PWD/config"
  $ public-inbox-init -V1 test test/ \
     http://localhost:8080/test test@public-inbox.org
  $ public-inbox-index -v test
  $ public-inbox-httpd &

  $ curl -fsS http://localhost:8080/manifest.js.gz | zcat | jq
  {}

On 08b649735, the output is

  {
    "/test": {
      "reference": null,
      ...
    }
  }

Bisecting with the script below points to 520be116 (www_listing: start
updating for pagination + search, 2021-06-23).

--8<---------------cut here---------------start------------->8---
#!/bin/sh

perl Makefile.PL && make && sudo make install || exit 125

# Local clone of https://try.public-inbox.org/test
pi_test=/tmp/pi-test

cd "$(mktemp -d "${TMPDIR:-/tmp}"/pi-XXXXXXX)"

export PI_CONFIG="$PWD/config"

git clone --mirror "$pi_test" test
public-inbox-init -V1 test test/ \
                  http://localhost:8080/test test@public-inbox.org
public-inbox-index -v test

trap 'trap - TERM && pkill -P $$' INT TERM EXIT
public-inbox-httpd &

sleep 1

curl -fsS http://localhost:8080/manifest.js.gz | zcat | jq -e '.["/test"]'
--8<---------------cut here---------------end--------------->8---

             reply	other threads:[~2021-06-27 20:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-27 20:28 Kyle Meyer [this message]
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 ` empty /manifest.js.gz response as of 520be116 Konstantin Ryabitsev
2021-06-30  2:38   ` 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=87fsx3128a.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.
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).