{"push_id":1291247647,"size":1,"distinct_size":1,"ref":"refs/heads/master","head":"2295056d00b6fedfc32a15af3020eea11a1c8d7a","before":"18af53bc61333286b2449a19e7e8c18c7d61520e","commits":[{"sha":"2295056d00b6fedfc32a15af3020eea11a1c8d7a","author":{"name":"hbhanawat","email":"bc75de3f5928c8f27acba7c32910b51b8998fc4c@gmail.com"},"message":"Ensuring that Spark Uncaught exceptions are handled in the Snappy side and do not cause a system.exit (#342)\n\nSnappyUncaughtExceptionHandler is now set as the uncaught exception handler in the executor. SnappyUncaughtExceptionHandler exits the executor component unlike the SparkUncaughtExceptionHandler which does a System.exit.\r\n\r\nWhile exiting the executor, check if snappy store is shutting down. If yes, there is no need to restart the executor.\r\n\r\nPatch testing\r\n\r\nAdded a test that tests restarting of executors because of an uncaught thread exception.\r\nAdded a test that tests restarting of executors because of an executor going down because of a fatal error.","distinct":true,"url":"https://api.github.com/repos/SnappyDataInc/snappydata/commits/2295056d00b6fedfc32a15af3020eea11a1c8d7a"}]}
{"actor":{"display_login":"hbhanawat"}}