Still alive

[opravil-jan]

Hello,

is this project still maintained?

Thank you
Jan Opravil

[MiroHibler]

Anyone?

[Shpadoinkle]

what is an alternative to this package? Seems abandoned, so will have to update current projects.

[Jonahss]

I forked this repo and replaced pg-ipc with pg-listen
So now it will retry the connection to postgres.

https://github.com/originlabs/graphql-postgres-subscriptions

Published to npm as @originlabs/graphql-postgres-subscriptions-retry

[raymclee]

I forked this repo and replaced pg-ipc with pg-listen
So now it will retry the connection to postgres.

https://github.com/originlabs/graphql-postgres-subscriptions

Published to npm as @originlabs/graphql-postgres-subscriptions-retry

hi @Jonahss

i have tried your fork but the pubsub never get connected.
no problem with the original package tho.

[Jonahss]

Hi @raymclee
If you send me sample code of your use-case I could take a quick look to see what could be wrong.
If you're using the asyncIterator, you have to pass in a list of topics in the constructor, that could be it.

I'm using my fork in production, so works for my case, but I'd be happy to fix any issues to work for your case.

[raymclee]

Hi @Jonahss, just tried again with topics added and it works!
not sure why it was not working last time. i think i have added the list of topics to constructor also.

[Jonahss]

Awesome! Yeah, I did the work pretty quickly, so had to make that requirement. It feels a little awkward, but I didn't want to change the interface too much, so that it's almost a drop-in replacement. If you want to dynamically add new topics, we might have to re-work it.

…

On Tue, Apr 20, 2021 at 6:00 AM raymclee ***@***.***> wrote: Hi @Jonahss <https://github.com/Jonahss>, just tried again with topics added and it works! not sure why it was not working last time. i think i have added the list of topics to constructor also. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#18 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AALTRMM6U4LF3I6Z7U75AKDTJV3HVANCNFSM4IFRGWCA> .

[chevsunpower]

@Jonahss Thanks a ton for this. Saved my bacon today after I thought I got a feature done with plenty of time for a demo tomorrow only to find that the AWS load balancer was destroying my websocket usage when deployed to the hosted environment. Then I found this repo and it's so out of date that nothing worked. Figured I was done for until I found your fork. Worked great. Thanks!

PS - I did run into the same issue as raymclee above. Had to come up with a work around because I was indeed using dynamic topics. My current implementation isn't the greatest because I just moved the dynamic bit to the payload and the client now receives all the payloads under that topic and then filters off of the value. When I have more time I'll try to PR in some dynamic topic support to your fork. For now it works fine for demo though so I'm finally off to bed! 😅

[Jonahss]

Hey sweet! Thanks for the shoutout :D Happy that more people are able to get graphql postgres subscriptions working. A nice solution to dynamic topics would be great.

…

On Thu, Aug 25, 2022 at 10:24 AM Chev ***@***.***> wrote: @Jonahss <https://github.com/Jonahss> Thanks a ton for this. Saved my bacon today after I thought I got a feature done with plenty of time for a demo tomorrow only to find that the AWS load balancer was destroying my websocket usage when deployed to the hosted environment. Then I found this repo and it's so out of date that nothing worked. Figured I was done for until I found your fork. Worked great. Thanks! PS - I did run into the same issue as raymclee above. Had to come up with a work around because I was indeed using dynamic topics. My current implementation isn't the greatest because I just moved the dynamic bit to the payload and the client now receives all the payloads under that topic and then filters off of the value. When I have more time I'll try to PR in some dynamic topic support to your fork. — Reply to this email directly, view it on GitHub <#18 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AALTRMLPEGNOLLYXE3PFQFTV24NS7ANCNFSM4IFRGWCA> . You are receiving this because you were mentioned.Message ID: ***@***.*** .com>