{"push_id":1625217974,"size":2,"distinct_size":2,"ref":"refs/heads/master","head":"9e072c19694989cd31c0b49fd103fe483dc70f58","before":"d4219678184fb908f7300b1b04a7fb34ee8d7c20","commits":[{"sha":"bb93c27d8d073d59f8474deb585121aa46e63d64","author":{"name":"Mathias Fussenegger","email":"bb3637c24a3a37def2478baea23f3a63a3cb44bb@zignar.net"},"message":"Improve kill handling in CollectingBatchIterator/AsyncOperationBatchIterator\n\nCollectingBatchIterator now forwards the kill call to its source instead\nof cancelling the future, in order to give the source the chance to\nhandle the kill itself.\n\nAsyncOperationBatchIterator will now check the killed state if\n`processBatch` fails and in case it was killed prefer the killed\nexception over the `processBatch` failure.\n\nIn the fetch-operation case a user invoked kill might remove the\nFetchContext which causes `processBatch` to fail with a context not\nfound exception.\nThis led to the user getting this context not found exception instead of\nthe expected \"job killed\" error.\n\nThis doesn't solve the issue completely as there is still a race\ncondition where the handler-node receives the kill request *after* a\nnode with a FetchContext has already been killed and led to the error.","distinct":true,"url":"https://api.github.com/repos/EvilMcJerkface/crate/commits/bb93c27d8d073d59f8474deb585121aa46e63d64"},{"sha":"9e072c19694989cd31c0b49fd103fe483dc70f58","author":{"name":"Naomi Slater","email":"2f90f67912033c483b037991823adb8931cfbc86@tumbolia.org"},"message":"release notes structure","distinct":true,"url":"https://api.github.com/repos/EvilMcJerkface/crate/commits/9e072c19694989cd31c0b49fd103fe483dc70f58"}]}
{"actor":{"display_login":"EvilMcJerkface"}}