Replies: 7 comments
-
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Beta Was this translation helpful? Give feedback.
-
Nope, stale! |
Beta Was this translation helpful? Give feedback.
-
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Beta Was this translation helpful? Give feedback.
-
Nope, stale. |
Beta Was this translation helpful? Give feedback.
-
@adrianlzt, did you find that removing the line in your PR worked? It seems for us that even when we remove this line, the apollo client still disconnects after the timeout. However, when we adjust the minTimeout the break occurs later. |
Beta Was this translation helpful? Give feedback.
-
Yes, it worked correctly without that line |
Beta Was this translation helpful? Give feedback.
-
Ran into this as well, and I'm not sure if our gqlgen setup was wrong, but the issue turned out to be that gqlgen by default doesn't send any keepalives after the initial connection. After setting |
Beta Was this translation helpful? Give feedback.
-
What happened?
Using an apollo client to connect to a subscription, each 20s the client is disconnected.
The disconections is initiated by the apollo client.
Comparing the behaviour between the glqgen server and the apollo server, gqlgen sends always a connectionKeepAliveMsg in the connection initialization.
I don't know why this "breaks" the apollo client. Maybe if it sees a KA msg it expected more to come?
What did you expect?
Compatibility with apollo client
Minimal graphql.schema and models to reproduce
versions
gqlgen version
? v0.11.3go version
? go1.14.2Beta Was this translation helpful? Give feedback.
All reactions