The same message is fired twice while we only make one subscription.
in a graphql mutation, we publish message abc to channel hell-no
Somehow, in the subscription that listens to new message from channel hell-no, we get message abc twice. We only saw this when rabbitmq server was deployed first time. After restarting the rabbitmq server, everything works fine.
Do you have any clue why this happens?
I have the same kind of issues when pubsub is reconnecting after a disconnection. Could be related to : https://github.com/apollographql/subscriptions-transport-ws/issues/458
please take a look at PR #12 that IMO fixes the problem
If the PR #12 fixes let us know, so i can merge it.