Mugetsu
Explore posts from serversController is already closed crash
So after some digging I found that the fetch request inside the tRPC procedure is causing this error to happen. It's not clear to me why this happens but when I have such procedure
And I do manually refresh my app (browser refresh) fast enough multiple times in a row the query errors and then it throws
Invalid state: Controller is already closed
and crash the app. When I just remove the fetch call it never throws that controller error but I still can see enigmatic error for the query in the console.7 replies
tRPC onError
OnError handler should be setup with your Fastify adapter for tRPC.
https://trpc.io/docs/server/adapters/fastify#create-fastify-server
4 replies
Stack trace in Client?
I've checked and NODE_ENV is production. I've also double checked this with the https://github.com/t3-oss/create-t3-app and trpc integration and its the same. The stack is displayed with loggerLink although I believe that this stack trace is related to client stack and should not be a big concern ???
6 replies
express-session for tRPC
You need an adapter with next-auth. I see u use redis with express. Then either use up-stash adapter for redis or you need to roll out your own adapter for redis. There is custom adapter for redis on next-auth issues or discussions as I was in need for one too. You have to look for it
https://next-auth.js.org/adapters
https://authjs.dev/reference/adapter/upstash-redis
https://authjs.dev/guides/adapters/using-a-database-adapter
https://authjs.dev/concepts/faq#databases
https://authjs.dev/reference/adapters
9 replies