From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: Eric Wong <e@80x24.org>
Cc: meta@public-inbox.org
Subject: Re: Occasional web view corruption (extra html escapes)
Date: Tue, 3 Sep 2024 15:18:21 -0400 [thread overview]
Message-ID: <20240903-rousing-black-tortoise-4c9ebb@meerkat> (raw)
In-Reply-To: <20240903184252.M951458@dcvr>
On Tue, Sep 03, 2024 at 06:42:52PM GMT, Eric Wong wrote:
> Konstantin Ryabitsev <konstantin@linuxfoundation.org> wrote:
> > This is only fixed by terminating the public-inbox-httpd process and letting it respawn.
> > This affects *all* web views for all messages, so likely some kind of state bug?
>
> Very strange, yes. Is it a frequent occurence? It only started
> hapening recently? It probably happened with some of the memory
> fragmentation reduction changes...
I've recently migrated all lore.kernel.org instances to RHEL9, switching to
the latest public-inbox master in the process -- so the best and the least
useful answer I can give you is "it started happening after I've changed
pretty much everything."
Thus far, I've seen this happen twice, both times on the same node.
-K
next prev parent reply other threads:[~2024-09-03 19:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-03 17:52 Occasional web view corruption (extra html escapes) Konstantin Ryabitsev
2024-09-03 18:42 ` Eric Wong
2024-09-03 19:18 ` Konstantin Ryabitsev [this message]
2024-09-03 19:11 ` Eric Wong
2024-09-03 19:22 ` Konstantin Ryabitsev
2024-09-04 13:14 ` Eric Wong
2024-09-04 14:42 ` Konstantin Ryabitsev
2024-09-06 22:20 ` Filip Hejsek
2024-09-06 22:42 ` Eric Wong
2024-09-06 23:29 ` Eric Wong
2024-09-07 1:24 ` Konstantin Ryabitsev
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=20240903-rousing-black-tortoise-4c9ebb@meerkat \
--to=konstantin@linuxfoundation.org \
--cc=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).