From: Eric Wong <e@80x24.org>
To: meta@public-inbox.org
Subject: [PATCH 0/6] test updates + coderepo removal workaround
Date: Mon, 30 Sep 2024 21:30:02 +0000 [thread overview]
Message-ID: <20240930213008.4014512-1-e@80x24.org> (raw)
For instances using -httpd||-netd, coderepos disappearing should
be better handled now.
We should probably handle disappearing inboxes at some point, too.
I also have yet to test new coderepos appearing, but I seem
to recall that works for projects.list users...
Inboxes appearing while -httpd||-netd is running is another
question that's unresolved, since we need to load the entire
config (and associated system-wide settings to deal with it).
Eric Wong (6):
t/www_static: modernize test
t/www_static: test with our -httpd server, too
t/www_static: ensure If-Modified-Since handling works
www: improve handling of missing coderepos
xt/solver: use `psgi' shortcut for require_mods()
t/{config,solver_git}: simplify error handling
lib/PublicInbox/Config.pm | 7 ++-
lib/PublicInbox/Git.pm | 4 +-
lib/PublicInbox/TestCommon.pm | 6 +-
t/config.t | 18 +++---
t/solver_git.t | 66 +++++++++++++++-------
t/www_static.t | 102 +++++++++++++++++++++++++---------
xt/solver.t | 4 +-
7 files changed, 145 insertions(+), 62 deletions(-)
next reply other threads:[~2024-09-30 21:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-30 21:30 Eric Wong [this message]
2024-09-30 21:30 ` [PATCH 1/6] t/www_static: modernize test Eric Wong
2024-09-30 21:30 ` [PATCH 2/6] t/www_static: test with our -httpd server, too Eric Wong
2024-09-30 21:30 ` [PATCH 3/6] t/www_static: ensure If-Modified-Since handling works Eric Wong
2024-09-30 21:30 ` [PATCH 4/6] www: improve handling of missing coderepos Eric Wong
2024-09-30 21:30 ` [PATCH 5/6] xt/solver: use `psgi' shortcut for require_mods() Eric Wong
2024-09-30 21:30 ` [PATCH 6/6] t/{config,solver_git}: simplify error handling 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=20240930213008.4014512-1-e@80x24.org \
--to=e@80x24.org \
--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).