-
Notifications
You must be signed in to change notification settings - Fork 18
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
TypeError: fetch failed] { cause: [Error: AggregateError] } #127
Comments
Thanks for the report. There's an example project using HTTP on Vercel Edge Functions at https://github.com/neondatabase-labs/neon-vercel-http/blob/main/api/sites.ts, and deployed at https://neon-vercel-http-pn9w6ym59-jawjs-projects.vercel.app. I just updated it to the latest driver version, and it seems to be working OK. The first thing to check is probably just that the |
@jawj POSTGRES_URL_NON_POOLING works with Kysely, but with one-shot query directly using Neon does not work. |
I'm happy to investigate this but first I need something I can reproduce. As I mentioned, our own example app using http from Vercel Edge Functions is working fine. |
@jawj Maybe this is because I'm running Neon locally in Docker. Also, the query is quite complex and with Kysely executeQuery it tries to use CompressionStream, which is not available in Edge Runtime. |
Steps to reproduce
Expected result
Return rows
Actual result
Error
Environment
Vercel Edge Runtime
Logs, links
Work with Kysely and Pool, but this does not work:
The text was updated successfully, but these errors were encountered: