-
Notifications
You must be signed in to change notification settings - Fork 190
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Application error: a client-side exception has occurred (see the browser console for more information). #94
Comments
Thanks for reporting @beejaz and apologies for the delay. It looks like that error is related to the SQL parser we are using. The fact that this is crashing the entire site is definitely not good. Let me investigate the error handling behind this first, then hopefully we will be able to retrieve the original queries you ran to identify what went wrong. |
Hi @gregnr appreciate you taking time to look into this. I've had issues accessing postgres.new from my home, but I managed it today and noticed its being migrated to database.build. I did an export from old site and imported to new site. After import, i tried visiting my first available database which was https://database.build/db/0taevgl1r2h50y0m and got the same error for https://database.build/db/0taevgl1r2h50y0m :
Console saying:
I get this error for every previous database I try to load (the imported ones). Including https://database.build/db/qqeztktg6u9hu8oe Hit me up if you need me to troubleshoot more. PS. creating a new basic database task and accessing it works. https://database.build/db/0w24ugr31o74tou8 |
Thanks for the details @beejaz. Can you confirm whether or not this same DB works on the old postgres.new domain, or does it crash there too with the If it works on postgres.new, can you share the migrations (via Migrations tab) for that DB? |
@gregnr Hey! Sorry, I wasnt aware that it was possible to access the old postgres.new now, I thought I was forced to export. It DOES work with https://postgres.new/db/qqeztktg6u9hu8oe on the old domain now. Here is the migrations from that one:
This is the previous task I gave it that caused the crash:
Executed SQL: select
id,
description
from
dishes; Generated embeddings:
Error executing SQL:
|
Amazing, thanks! Yes postgres.new will be available for a short period, but soon folks will be redirected to database.build. Good news - I think I've identified the issue 😄 it's related to a bug when importing DBs into database.build. I have a fix in place in #127. If you don't mind, would mind testing your imports on this preview branch to see if it solves it for you? If so we'll merge that to prod: Import URLhttps://postgres-new-git-fix-message-import-supabase.vercel.app/import Main URLhttps://postgres-new-git-fix-message-import-supabase.vercel.app |
I tested this using a DB export provided from another report who experienced the same issue, and all works correctly now. We'll merge this to prod now, but do let me know if you still experience errors! |
@gregnr The database import works on that staging branch 👌 Sorry for late reply, hopefully I didnt block anything. Thank you for your help, awesome product and great work to you and the team! |
Bug report
Describe the bug
Created some tables, asked to fill it with dummy data, asked to fill some additional embeddings dummy data. Site crashed.
Going to the postgres.new shows previous stored conversation but when I load it, it crashes the website again. Similar to #52
Console shows (super long error message):
To Reproduce
I cant access the conversation so I cant tell exacly what I did, if it helps, the DB ID is
qqeztktg6u9hu8oe
Expected behavior
Application is accessable, loading previous conversation works and doesnt crash the deploy.
Screenshots
System information
Additional context
I can provide full console log if it helps, its super long. I also managed to download the database from the UI.
The text was updated successfully, but these errors were encountered: