Re: mbox/pgsql-hackers.202003 missing all messages after 2020-03-09

On Thu, Aug 6, 2020 at 9:45 AM Noah Misch <noah(at)leadboat(dot)com> wrote:

> On Fri, Apr 10, 2020 at 09:32:46PM -0700, Noah Misch wrote:
> > On Fri, Apr 10, 2020 at 05:30:03PM +0200, Magnus Hagander wrote:
> > > On Wed, Apr 8, 2020 at 8:20 AM Noah Misch <noah(at)leadboat(dot)com> wrote:
> > > >
> https://www.postgresql.org/list/pgsql-hackers/mbox/pgsql-hackers.202003 is
> > > > missing all messages after 2020-03-09. pgsql-bugs.202003 and
> > > > pgsql-hackers.202004 are fine.
> > >
> > > It looks like there was an email in the archives exactly on the 9th
> that
> > > somehow confused the python mbox generating code into just stopping
> there.
> > > I've marked that message as corrupt, and AFAICT it now happily
> downloads
> > > the full mbox.
> >
> > Confirmed. Thanks.
>
> https://www.postgresql.org/list/pgsql-hackers/mbox/pgsql-hackers.202007
> has
> its latest message from 2020-07-08. Did the same sort of cause recur?
>

Yeah, same thing again, there was a corrupt message in the archive that
made it blow up. It's annoying that it just stops there and doesn't
actually produce an error :/

In this particular case, it was git-send-email setting
content-transfer-encoding to 8bit and then passing utf8 data in there. This
is most likely a client side configuration error, I guess, but it'd be good
if we can somehow deal with it without blowing up.

--
Magnus Hagander
Me: https://www.hagander.net/ <http://www.hagander.net/>
Work: https://www.redpill-linpro.com/ <http://www.redpill-linpro.com/>