You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm using the HttpClientGitHubConnector to make HTTP/2 requests to the GitHub API. Occasionally, a request fails with "GOAWAY received". I'm not sure when GitHub sends a GOAWAY frame.
Is this another way that GitHub communicates secondary rate limits?
Is this a GitHub outage?
Is this GitHub telling the app that it has kept its HTTP/2 connection open for too long?
Has anyone else identified a pattern in when GitHub sends a GOAWAY? Would it be appropriate to add retries into the HttpClientGitHubConnector to handle GOAWAY?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I'm using the
HttpClientGitHubConnector
to make HTTP/2 requests to the GitHub API. Occasionally, a request fails with "GOAWAY received". I'm not sure when GitHub sends a GOAWAY frame.Has anyone else identified a pattern in when GitHub sends a GOAWAY? Would it be appropriate to add retries into the
HttpClientGitHubConnector
to handle GOAWAY?Beta Was this translation helpful? Give feedback.
All reactions