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
Problem:
We are running the gosmee server on Azure App Services, and the Azure Loadbalancer in front serving these applications has a default non-changable connection-timeout of 230 seconds. This means with the SSE setup of gosmee, that we every ~4 minutes get a connection reset by peer on the gosmee client.
Currently it seems like the default is to retry the connection 5 or 4 times before gosmee exists. This in turn causes the container the gosmee client runs in to restart every 20 minutes, and until the container is back up, we can potentially loose events from in our case github.
Feature request:
Make it possible to control the retry settings to avoid the conainer restarts, or in some way handle these connection resets from Azure App service without exiting the gosmee binary.
The text was updated successfully, but these errors were encountered:
Problem:
We are running the gosmee server on Azure App Services, and the Azure Loadbalancer in front serving these applications has a default non-changable connection-timeout of 230 seconds. This means with the SSE setup of gosmee, that we every ~4 minutes get a connection reset by peer on the gosmee client.
Currently it seems like the default is to retry the connection 5 or 4 times before gosmee exists. This in turn causes the container the gosmee client runs in to restart every 20 minutes, and until the container is back up, we can potentially loose events from in our case github.
Feature request:
Make it possible to control the retry settings to avoid the conainer restarts, or in some way handle these connection resets from Azure App service without exiting the gosmee binary.
The text was updated successfully, but these errors were encountered: