9 Replies
Ok I'm losing my mind, prisma pulse just randomly disconnects
No error messages or anything
I've been debugging this for the last hour
it doesn't seem that we're getting disconnected from the websocket, becuase the ping/pongs are still alive
and the events are hitting prisma, as the counter in the dashboard goes up
yet if I spam some database events it eventually fries like this
and I can't get events anymore.
Yeah this has to be you guys crashing
Welp, I'm upgraded to 1.2.0, using a minimal example. Yet this still breaks. I'm fine if it crashes but seemingly this is crashing on your backend somwhere and not on my client code. So I have no way of telling that this errored.
well subscribe works fine, but this will cause a lot of problems for us
as event order is really important
other option is to just reset stream every 5m.
Hey @Jake
Can you share your email or GitHub handle with us?
I would like to take a look at the logs for your project.
Do you have multiple steams with the same name or different names?
[email protected]
jwd-dev
@Nurul (Prisma)
It would break with single streams, single named streams, multiple unnamed streams, multiple streams with different names
Any update here? @Nurul (Prisma)
Hey @Jake
Apologies for the delay in getting back to you.
I see that you have 3 environments "Production", "Development" and "Staging" for your workspace "Respell".
I can see that substantial number of events on Trigger table are ingested for the "Production" workspace. I also noticed that the database connection is active.
Can you share with me the entire error stack trace that you get when the connection gets disconnected? How often does this happen?
I'll share these with our Pulse team to get this sorted out.
No error stack trace
@Nurul (Prisma) could you have your team reach out to me over my work email? [email protected]
I really don't use discord for business use cases.