Closed kate-mills closed 5 years ago
Hi team, Boris form DeepCode here. We noticed (thanks @babybunny for reporting) that our service is blocking you. Usually, DeepCode takes seconds to analyze a Pull Request, but your Pull requests have invertedly ended-up in a strange state. Our team is looking into it and we will report here shortly. If you need me, in the meantime you can reach me at boris@deepcode.ai
retry deepcode
DeepCode analyzed this pull request. There are no new issues.
vraychev above manually restarted the check by DeepCode and this completed. Apologies for the delay, we had an obscure bug that prevented us to alert GitHub that the analysis completed. On average our analysis completes in 1 to 2 seconds. So please do let us know if you experience any future problems or have other feedback: deepcode@deepcode.ai
Thanks for fixing it! Good to know also that this was a strange state and nothing to expect in the future. Are you putting any alerts on place in case a similar situation occurs?
On Wed, Mar 27, 2019, 9:08 AM thebpc notifications@github.com wrote:
vraychev above manually restarted the check by DeepCode and this completed. Apologies for the delay, we had an obscure bug that prevented us to alert GitHub that the analysis completed. On average our analysis completes in 1 to 2 seconds. So please do let us know if you experience any future problems or have other feedback: deepcode@deepcode.ai
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/babybunny/rebuildingtogethercaptain/pull/511#issuecomment-477229777, or mute the thread https://github.com/notifications/unsubscribe-auth/AK-yPMN1jlukmTU1eCwTd5B516YX7mQTks5va5ePgaJpZM4cMpJc .
Yes indeed, we will be tracking state internally so if there is a restart or other weird events causing a process to end-up not closing we will be automatically restarting it.
On Fri, Mar 29, 2019 at 11:53 PM Luke Stone notifications@github.com wrote:
Thanks for fixing it! Good to know also that this was a strange state and nothing to expect in the future. Are you putting any alerts on place in case a similar situation occurs?
On Wed, Mar 27, 2019, 9:08 AM thebpc notifications@github.com wrote:
vraychev above manually restarted the check by DeepCode and this completed. Apologies for the delay, we had an obscure bug that prevented us to alert GitHub that the analysis completed. On average our analysis completes in 1 to 2 seconds. So please do let us know if you experience any future problems or have other feedback: deepcode@deepcode.ai
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub < https://github.com/babybunny/rebuildingtogethercaptain/pull/511#issuecomment-477229777 , or mute the thread < https://github.com/notifications/unsubscribe-auth/AK-yPMN1jlukmTU1eCwTd5B516YX7mQTks5va5ePgaJpZM4cMpJc
.
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/babybunny/rebuildingtogethercaptain/pull/511#issuecomment-478173002, or mute the thread https://github.com/notifications/unsubscribe-auth/AheeZWMEVEwC7_TeNbMZen4Iu5Vrwp9aks5vbplxgaJpZM4cMpJc .
Hope this is is what you were wanting.