PostgREST v14.15 arm64 container returns plain-text 500 for UTF-8 PostgreSQL error messages without locale
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 48/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- postgresql, typescript
Research direction
Start by reproducing the direct request against the arm64 PostgREST v14.15 container with locale C and an accented PostgreSQL error, then compare stderr and the HTTP response with LC_ALL=C.utf8 or logging suppressed. Done means the arm64 image returns the JSON error and preserves the complete UTF-8 log, with amd64 behavior assessed for parity.
Written by the indexing model from the issue text.
Description
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.
- Dominant language
- TypeScript
- Stars
- 2.4k
- Forks
- 526
- Avg merge
- 1d 2h
- Merged PRs (30d)
- 307
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from supabase/cli
-
🐛 Bug supabase/cli
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
SQL statement splitter breaks E'...' strings that contain a backslash-escaped quotePossibly taken @7ttp claimed this 1 day ago. Open🐛 Bug supabase/cli
supabase/cli#6885 · 1 assignee ·
Maintainers usually reply within 1 day
-
db push applies migrations when the confirmation answer is not yes or noPossibly taken @7ttp claimed this 2 days ago. Open🐛 Bug supabase/cli
supabase/cli#6869 · 1 assignee ·
Maintainers usually reply within 1 day
-
🐛 Bug supabase/cli
Difficulty 4/5 3-5 days Newbie friendliness 35/100
Maintainers usually reply within 1 day
-
🐛 Bug supabase/cli
Difficulty 4/5 3-5 days Newbie friendliness 35/100
Maintainers usually reply within 1 day
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 78/100
lichess-org/api#678 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
PostHog/posthog.com#20628 ·
Maintainers usually reply within 1 day
-
bug status:Needs Triage
Difficulty 1/5 Under an hour Newbie friendliness 92/100
jupyterlab/jupyterlab#19964 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
agentscope-ai/QwenPaw#8064 · 1 comment ·
Maintainers usually reply within 1 day
-
area: notebooks-jupyter bug theme: new notebook frontend
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
posit-dev/positron#16347 · 1 comment ·
Maintainers usually reply within 1 day