{"push_id":1794190771,"size":2,"distinct_size":2,"ref":"refs/heads/3.0","head":"b3499589235a793a56dea1422f94392af1012a51","before":"6f252366f78695a467b551ec0b2d372d2ce62c07","commits":[{"sha":"3758693ce475997844ee9e7e5cd1104dd5931e0b","author":{"name":"Paul Millar","email":"4a6a3bb8c9d01f48480af5e8f6480cef5e8e3747@desy.de"},"message":"pool: log why a transfer was forcefully aborted\n\nMotivation:\n\nA mover may be forcefully aborted for any number of reasons. Currently,\nthe pool's domain log shows only a place-holder text \"Transfer was\nforcefully killed\", which is also sent to billing.\n\nThis is almost certainly insufficient information to deduce what went\nwrong.  Although the door might (or might not) log more accurate\ninformation, providing the explanation when logging will likely improve\nthe speed with which admin can diagnose problems.\n\nModification:\n\nLog the reason why a transfer was aborted: both in the domain log file\nand in billing.\n\nNote that the door's report of the failed transfer may contain duplicate\ninformation.\n\nResult:\n\nMore accurate information is available when transfers fail.\n\nTarget: master\nRequest: 3.1\nRequest: 3.0\nRequires-notes: yes\nRequires-book: no\nPatch: https://rb.dcache.org/r/10219/\nAcked-by: Tigran Mkrtchyan","distinct":true,"url":"https://api.github.com/repos/dCache/dcache/commits/3758693ce475997844ee9e7e5cd1104dd5931e0b"},{"sha":"b3499589235a793a56dea1422f94392af1012a51","author":{"name":"mksahakyan","email":"29ac2c586852fd0164328467415bdab6908e7b48@desy.de"},"message":"Merge pull request #3216 from paulmillar/fix/3.0/rb10219\n\npool: log why a transfer was forcefully aborted","distinct":true,"url":"https://api.github.com/repos/dCache/dcache/commits/b3499589235a793a56dea1422f94392af1012a51"}]}
{"actor":{"display_login":"mksahakyan"}}