99designs / gqlgen

go generate based graphql server library
https://gqlgen.com
MIT License
9.88k stars 1.15k forks source link

Strange situation after closing subscription connection from playground #952

Open emeno89 opened 4 years ago

emeno89 commented 4 years ago

What happened?

"ka" frame sending from server to client (graphql web playground) after closing connection ("stop" frame).

What did you expect?

Connection fully closed, "stop" frame from client and "complete" frame from server are last.

Minimal graphql.schema and models to reproduce

type Subscription { recommendations: RecommendationElement! }

union RecommendationElement = InfoPopup

type InfoPopup { title: String! }

versions

Hello!

We have one issue with webSocket subscriptions, which reproduced constantly with GraphIQL (Playground):

1) Playground establish connection with server, first frames are "connection init", "start" and "connection_ack"; 2) Then server sends some "ka" frames (we use keep alive duration 10 seconds); 3) Then connection stops, using Playground stop button, client sends "stop" and server answers "complete"; 4) After this "ka" frames continue coming to client, and this process stopped only, when Web-Server (we use Ingress in GKE), closed client->server connection after timeout;

image

Seems, "ka" frames ticker must be stopped after "stop" and "complete" message, because go routine continue work without any profit.

Would you help us to solve this problem? Thanks.

stale[bot] commented 4 years ago

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.

zhChenOuO commented 2 years ago

I have the same problem

xbassols commented 2 years ago

I just stumbled with the same thing while looking why the client wasn't disconnecting or reconnecting after an error.

rootkea commented 1 year ago

I am not able to reproduce this issue with gqlgen 0.17.14.

First of all, I don't see any "ka" frames in spite of me setting the keep alive duration to 10 seconds.

Secondly, when I press the "Stop" button in GraphiQL web playground, client sends "complete", server responds with "complete" and then connection is closed normally.

Screenshot_2022-12-15_09-44-37