Feedback-ID: ia2694551:Fastmail
Date: Fri, 10 May 2024 13:59:39 +0200
From: Alvaro Herrera <alvherre@alvh.no-ip.org>
To: Michael Paquier <michael@paquier.xyz>
Cc: pgsql-hackers@lists.postgresql.org, 
	Jacob Champion <jacob.champion@enterprisedb.com>
Subject: Re: pgsql: Fix overread in JSON parsing errors for incomplete byte
 sequence
Message-ID: <202405101159.ttkbzrb5l7vn@alvherre.pgsql>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <E1s4ujr-0006aU-0Z@gemulon.postgresql.org>
Archived-At: <https://www.postgresql.org/message-id/202405101159.ttkbzrb5l7vn%40alvherre.pgsql>
Precedence: bulk

On 2024-May-09, Michael Paquier wrote:

> Fix overread in JSON parsing errors for incomplete byte sequences

I'm getting this error in the new test:

t/002_inline.pl ........................ 1/? 
#   Failed test 'incomplete UTF-8 sequence, chunk size 3: correct error output'
#   at t/002_inline.pl line 134.
#                   'Escape sequence "\�1+2" is invalid.'
#     doesn't match '(?^:(Token|Escape sequence) ""?\\\x{F5}" is invalid)'
# Looks like you failed 1 test of 850.

Not sure what's going on here, or why it fails for me while the
buildfarm is all happy.

-- 
Álvaro Herrera         PostgreSQL Developer  —  https://www.EnterpriseDB.com/
"Every machine is a smoke machine if you operate it wrong enough."
https://twitter.com/libseybieda/status/1541673325781196801