On macOS arm64/Colima, Supabase CLI 2.111.0 starts public.ecr.aws/supabase/postgrest:v14.15 (arm64) without LANG/LC_ALL. A PostgreSQL RPC that raises SQLSTATE 55P03 or P0002 with an accented UTF-8 message, mapped to HTTP 500, produces status 500 text/plain body "Something went wrong" rather than the JSON error. ASCII message with same SQLSTATE returns JSON, and accented message mapped to HTTP 400 returns JSON. Reproduces on direct request to PostgREST, bypassing Kong. Its stderr log for the failing case truncates at the accented character. In a temporary container with the same arm64 image, DB and PGRST config, adding LC_ALL=C.utf8 (or LANG=C.utf8) yields JSON and complete log; suppressing error log with PGRST_LOG_LEVEL=crit also yields JSON. Please ensure an UTF-8 locale for the arm64 image or make error logging robust to UTF-8 under locale C, and consider parity with the amd64 image. The tag's arm64 build is dynamic glibc while amd64 is static musl; we have NOT proven that the amd64 build behaves differently on this minimal repro. No credentials or private DB data needed in the issue.
On macOS arm64/Colima, Supabase CLI 2.111.0 starts public.ecr.aws/supabase/postgrest:v14.15 (arm64) without LANG/LC_ALL. A PostgreSQL RPC that raises SQLSTATE 55P03 or P0002 with an accented UTF-8 message, mapped to HTTP 500, produces status 500 text/plain body "Something went wrong" rather than the JSON error. ASCII message with same SQLSTATE returns JSON, and accented message mapped to HTTP 400 returns JSON. Reproduces on direct request to PostgREST, bypassing Kong. Its stderr log for the failing case truncates at the accented character. In a temporary container with the same arm64 image, DB and PGRST config, adding LC_ALL=C.utf8 (or LANG=C.utf8) yields JSON and complete log; suppressing error log with PGRST_LOG_LEVEL=crit also yields JSON. Please ensure an UTF-8 locale for the arm64 image or make error logging robust to UTF-8 under locale C, and consider parity with the amd64 image. The tag's arm64 build is dynamic glibc while amd64 is static musl; we have NOT proven that the amd64 build behaves differently on this minimal repro. No credentials or private DB data needed in the issue.