supabase: SQL Editor errors handling is broken

Describe the bug When entering some potentially failing SQL query into the Editor an entire page errors out with Next’s component showing Application error: a client-side exception has occurred (see the browser console for more information). message.

To Reproduce Steps to reproduce the behavior:

1. Go to the SQL Editor.
2. Enter a query that’s going to fail. For example, for me it was creating a view and selecting a column that doesn’t exist.

CREATE VIEW collection_page_artifacts AS
SELECT
	artifacts.*,
	collection_artifact.collection_id,
	collections.title,
	collections.user_id,
	collections.access,
        -- 'profiles' doesn't exist under 'collections', it's a separate table
	collections.profiles
FROM
	artifacts
INNER JOIN
	collection_artifact ON artifacts.id = collection_artifact.artifact_id
INNER JOIN
	collections ON collection_artifact.collection_id = collections.id
INNER JOIN
	profiles ON collections.user_id = profiles.id;

But I have this issue with literally every possible SQL query that’s incorrect, even if it’s just syntax error.

1. Run the query.

Expected behavior

• A query is run and the error is visible in the Results section.
• If that failed, I’d expect to go to Logs/Postgres and see the error log there, but as you can see in the second screenshot, the error/warning message looks scattered and broken down into other events with the same time stamp.

Screenshots

Desktop (please complete the following information):

• OS: macOS Sonoma 14.1.1
• Browser: Arc (Chromium) / Safari
• Version of CLI: 1.112.0

Additional context Worth mentioning that upon opening the SQL Editor page and entering some query, I have the “Failed to save” warning in the bottom right.