{"push_id":1153749410,"size":1,"distinct_size":1,"ref":"refs/heads/poormansvmci.kerneltime","head":"e4cb0b2112a568b6fa01d1035b6e729f5267223b","before":"aed0a2aa5dd4406c252a5ea490f14c20e7442c31","commits":[{"sha":"e4cb0b2112a568b6fa01d1035b6e729f5267223b","author":{"name":"Ritesh H Shukla","email":"3a6f22685d38070f814624fe3df7ee7326cda461@vmware.com"},"message":"Add additional logging for vmci failures. Fixes #207\n\nSince the cause of communication failures need more info than what can be packed into a log message. Forward the customer to the FAQ.\n\n```\n2016-06-11 00:15:06.869406637 +0530 IST [WARNING] 'list' failed: connection reset by peer (errno=104). Hit communication issue with ESX (vmci or ESX service)\n     Please refer to the FAQ https://github.com/vmware/docker-volume-vsphere/wiki#faq\n```","distinct":true,"url":"https://api.github.com/repos/vmware/docker-volume-vsphere/commits/e4cb0b2112a568b6fa01d1035b6e729f5267223b"}]}
{"actor":{"display_login":"kerneltime"}}