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
WebSockets connections issues arraybuffer? #77
Comments
Thanks for your report. It's a unfortunately opaque error message! If it persists, please let us know what platform you're running this on. A minimal reproduction would also be very helpful. That particular undici fix was eventually merged a while back, so in principle it should be fine now to use either ws or undici in that file. Is it possible your issue is down to a recent problem with pnpm? |
@jawj can you give me a brief explanation how to use / build & deploy the package locally? I would be able to track the error more precisely. The context is the following:
I am using the latest version of the package on npm 0.9.1 (0.9.2 is not deployed btw, if that matters) This is how the client is instantiated import { PrismaClient } from "@/prisma/generated/client";
import { Pool } from "@neondatabase/serverless";
import { PrismaNeon } from "@prisma/adapter-neon";
const pool = new Pool({ connectionString: process.env.POSTGRES_URL });
const adapter = new PrismaNeon(pool);
export const prisma = new PrismaClient({ adapter }); |
OK. Clone https://github.com/neondatabase/serverless and take a look at DEVELOP.md. After making changes, run In another project, run |
Hello, I am stumbeling on an periodical error, something like that:
Had to add a
console.log
to see it actually..Anyway, seems to be ws related, and wanted to ask, if this is something known, because I found this comment in the codebase:
serverless/dist/node/index.mjs
Line 6 in b39a2dd
It looks like undici already merged the fix, and btw some hours ago they published a new version.
If its not planned to use it immediately, I would like to try it out, should I just link this repo locally and try out?
The text was updated successfully, but these errors were encountered: