{"push_id":1561394277,"size":1,"distinct_size":1,"ref":"refs/heads/w/fix-absorb-cancellation","head":"dfa7dd9fcc957bae6e5cd4073252377c1a7bf9a9","before":"62a6046578346ca66d89bf6a18f238baab3abcff","commits":[{"sha":"dfa7dd9fcc957bae6e5cd4073252377c1a7bf9a9","author":{"name":"Johannes Rudolph","email":"1ed2c7cceb61c21c39080b0fa5a1b1604aad158b@gmail.com"},"message":"=htc #851 fix leaking AbsorbCancellation\n\nUnder circumstances that I could not reproduce so far,\nthe AbsorbCancellation stage introduced in #459 may keep the graph running\nif data was already buffered but never read. The reason is that the stage\nso far requires completion to reach the stage after cancellation was\nabsorbed which might be blocked by incoming elements that were never\npulled.\n\nThe solution is two-fold. After cancellation:\n\n 1) pull in and ignore all incoming elements to eventually fetch completion\n 2) complete the stage after a configurable time\n\nIn the HTTP use case, we delay the cancellation by no more than the time specified\nin the new linger-timeout setting.","distinct":true,"url":"https://api.github.com/repos/jrudolph/akka-http/commits/dfa7dd9fcc957bae6e5cd4073252377c1a7bf9a9"}]}
{"actor":{"display_login":"jrudolph"}}