Problem with Stream on Pulse
GM,
It was working in the past then we got some problem with NeonDB that have been fixed by Neon themselve
Currently I'm unable to use
We use a custom Publication created with this command
Which seems to work since I'm able to use
I added few log in the pulse lib directly :
So it look like Websocket work well and there is no problem on this side
Have you got any idea of what can happen here ?
Everything is setup looking at the doc, we use a ssl require with neon which should work, we have logical replication on Neon too, no IP allowance or things like this so must not be the problem
I searched the whole day to understand what happen but I think it's on DB level and I can't fix it on my side
If you need anymore code let me know, I downloaded the sample repo (basic stream without anything else) and stream doesn't work while subscribe work even in this case so can't be a NestJS problem too
(cc @kipit )
It was working in the past then we got some problem with NeonDB that have been fixed by Neon themselve
Currently I'm unable to use
stream()We use a custom Publication created with this command
Which seems to work since I'm able to use
subscribe()I added few log in the pulse lib directly :
So it look like Websocket work well and there is no problem on this side
Have you got any idea of what can happen here ?
Everything is setup looking at the doc, we use a ssl require with neon which should work, we have logical replication on Neon too, no IP allowance or things like this so must not be the problem
I searched the whole day to understand what happen but I think it's on DB level and I can't fix it on my side
If you need anymore code let me know, I downloaded the sample repo (basic stream without anything else) and stream doesn't work while subscribe work even in this case so can't be a NestJS problem too
(cc @kipit )
