graphql-redis-subscriptions
graphql-redis-subscriptions copied to clipboard
davidyaha
A graphql subscriptions implementation using redis and apollo's graphql-subscriptions
I noticed that github actions was complaining about old versions of these actions.
This updates the types so there's no need for a duplicate version from what's already in `graphql-subscriptions` (or was in the 3.0 release branch anyway, which I just released as...
We ran into a tricky race condition when `RedisPubSub` is handling multiple simultaneous `subscribe` calls on the same channel. We have a client that sometimes initiates multiple subscribe and quickly...
Updated my node version from node 14.16.0 to node 16.0.0. const { RedisPubSub } = require('graphql-redis-subscriptions/dist/redis-pubsub'); export const pubSub = new RedisPubSub({ publisher: new Redis(readOptions), subscriber: new Redis(readOptions), }) The...
Exports the type definitions for configuration so we don't need to import like this: `import type { PubSubRedisOptions } from 'graphql-redis-subscriptions/dist/redis-pubsub';`
ref: https://github.com/davidyaha/graphql-redis-subscriptions/issues/605
Is there a way to perform an action when a socket is closed using `asyncIterator`? I'd like to fire a method whenever the connection to the client is closed
Add an optional filterFn to PubSubAsyncIterator to workaround performance issues found in withFilter
Our production application filters a high number of messages, more than 99% are filtered out. We suffered an issue of unbounded memory growth caused by the behavior of `withFilter`. Our...
my redis-pub-sub.provider.ts like below ; ``` import { pubSubToken } from '@nestjs-query/query-graphql'; import { RedisPubSub } from 'graphql-redis-subscriptions'; import Redis from 'ioredis'; import { Provider } from '@nestjs/common'; export class...
We are currently investigating restarts of our pods, and upon investigating the logs prior to a restart we observe the following: ``` [pod/backend-production-5b8c657b85-blltz/backend-production] This error originated either by throwing inside...