public inbox for [email protected]  

help / color / mirror / Atom feed

From: Henson Choi <[email protected]>
To: Tatsuo Ishii <[email protected]>
Cc: [email protected]
Cc: [email protected]
Cc: [email protected]
Cc: [email protected]
Cc: [email protected]
Cc: [email protected]
Subject: Re: Row pattern recognition
Date: Wed, 4 Mar 2026 16:29:35 +0900
Message-ID: <CAAAe_zAk3zRy4e=St-_7jqUB1cbw08B6-4Giwr+1Ei570J0byg@mail.gmail.com> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
	<CAAAe_zCkpYn7qh=chxVLo4-HG8D57RwxhUq-c9zrYvZVtdDgeA@mail.gmail.com>
	<[email protected]>
	<[email protected]>

Hi Tatsuo,

CFBot complains v44-0007 patch corrupted.
> https://cfbot.cputube.org/patch_4460.log


I downloaded v44-0007 from the mailing list archive and applied it
successfully in my local environment. Everything works fine here.


> So it seems the file was truncated somwhere between me and PostgreSQL
> ML archiving.
>

It seems CFBot does not retry once it fails, so the initial truncation
error has become permanent.


> Can you check the size of the file attached to your mail?


I didn't check the raw attachment size, but the patch applied cleanly
without any issues.

To work around this, how about splitting the test patch (0007) into
separate patches for .sql and .out files? This would reduce the
individual file sizes and help avoid truncation during archiving.

Best regards,
Henson

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected]
  Subject: Re: Row pattern recognition
  In-Reply-To: <CAAAe_zAk3zRy4e=St-_7jqUB1cbw08B6-4Giwr+1Ei570J0byg@mail.gmail.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox