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
Probably Github is verifying that the webhook actually replies by senidng an empty message or opening/closing the socket.
I doubt it would be the Jenkins server - unless gosmee is polling Jenkins itself and receiving an empty reply?
It might be these are not seen in all situations.
This particular webhook is being used by both a Github Application and general organization wide gthub hook.
These are annoying since there is now a lot of unnecessary errors. Furthermore, ERROR looks really dangerous when in fact nothing has happened.
I can possibly get more debugging information if there is a flag to do that. FYI, I am running gosmee inside docker.
Can you fix this?
The text was updated successfully, but these errors were encountered:
Probably Github is verifying that the webhook actually replies by senidng an empty message or opening/closing the socket.
I doubt it would be the Jenkins server - unless gosmee is polling Jenkins itself and receiving an empty reply?
It might be these are not seen in all situations.
This particular webhook is being used by both a Github Application and general organization wide gthub hook.
These are annoying since there is now a lot of unnecessary errors. Furthermore, ERROR looks really dangerous when in fact nothing has happened.
I can possibly get more debugging information if there is a flag to do that. FYI, I am running gosmee inside docker.
Can you fix this?
The text was updated successfully, but these errors were encountered: