{"push_id":1413528094,"size":8,"distinct_size":8,"ref":"refs/heads/master","head":"8d536670baac799b2f0a2c0147650e264e17dbec","before":"083c3277bb3d918dd1c4f2fcc73552a39bae4ff9","commits":[{"sha":"fa475472a01d24c0d9d7709ed7ab33d28dd50d53","author":{"name":"Matt Klein","email":"e2f3e9cbb1e558e519f4db318e95796b7ab57055@users.noreply.github.com"},"message":"tcp proxy: fix connection/fd leak during local close (#228)\n\nThis can happen when the connection gets closed locally by another filter\r\n(e.g., the rate limit filter).\r\n\r\nThis is a regression from both c172a4 and a10174. The first commit makes it\r\nso that we create the upstream connection in the constructor and not when\r\nwe first have data. The second commit which removed bufferevent removes the\r\nsafeguard that would have happened in the destructor which would have closed\r\nthe fd in the bev.\r\n\r\nThis commit fixes the main leaking issue but also puts a failsafe into the\r\nconnection destructor such that we will close the fd always and be more likely\r\nto crash instead of keep going.","distinct":true,"url":"https://api.github.com/repos/amalgam8/envoy/commits/fa475472a01d24c0d9d7709ed7ab33d28dd50d53"},{"sha":"703b68680b985803a61139e52543b18656e79b43","author":{"name":"Roman Dzhabarov","email":"96386289442cb1074999d8b231965ccc3eb7096d@lyft.com"},"message":"Convert c-string to std::string as LightStep library does not treat c string well. (#229)","distinct":true,"url":"https://api.github.com/repos/amalgam8/envoy/commits/703b68680b985803a61139e52543b18656e79b43"},{"sha":"bb93ab7226fd6f0e7390aa008b474e00968577d3","author":{"name":"Roman Dzhabarov","email":"96386289442cb1074999d8b231965ccc3eb7096d@lyft.com"},"message":"perf: optimize zone aware load balancing (#227)","distinct":true,"url":"https://api.github.com/repos/amalgam8/envoy/commits/bb93ab7226fd6f0e7390aa008b474e00968577d3"},{"sha":"67ca72cff65cddc578cbed2e31e60f34dd7cb0a8","author":{"name":"Matt Klein","email":"e2f3e9cbb1e558e519f4db318e95796b7ab57055@users.noreply.github.com"},"message":"perf: various fixes to reduce allocations (#230)\n\n1) Use vector in thread local vs map\r\n2) Remove extra allocation for each request from codec client\r\n3) remove extra allocation for each request from http/1.1 conn pool\r\n4) Use vector for stream reset callbacks","distinct":true,"url":"https://api.github.com/repos/amalgam8/envoy/commits/67ca72cff65cddc578cbed2e31e60f34dd7cb0a8"},{"sha":"3a8059184392c2fd7a8b8659893ff52c7031bd5c","author":{"name":"Matt Klein","email":"e2f3e9cbb1e558e519f4db318e95796b7ab57055@users.noreply.github.com"},"message":"perf: http/1 use table for lower case conversion (#231)","distinct":true,"url":"https://api.github.com/repos/amalgam8/envoy/commits/3a8059184392c2fd7a8b8659893ff52c7031bd5c"},{"sha":"7e57daa9c6cb82c936c34bf5470b1a7508798f6d","author":{"name":"Matt Klein","email":"e2f3e9cbb1e558e519f4db318e95796b7ab57055@users.noreply.github.com"},"message":"network filters: add onNewConnection() callback (#233)\n\nThis is more fallout from c172a4. For network filters we want the\r\nability to do things when the connection is created, but also to\r\nallow stopping iterations of further filters. In the previous change,\r\nwe made it so that the proxy filter will always make a new connection\r\nto upstream regardless of what other filters do. We change that now\r\nsuch that the tcp proxy filter will only make the upstream connection\r\nin the onNewConnection() callback. Other filters (currently client_ssl\r\nand ratelimit) now do their work on their own onNewConnection() callback\r\nand stop iteration if necessary to prevent the tcp proxy filter from\r\nmaking the upstream connection until it is supposed to.","distinct":true,"url":"https://api.github.com/repos/amalgam8/envoy/commits/7e57daa9c6cb82c936c34bf5470b1a7508798f6d"},{"sha":"4090ba297aa76deea11b526f455c294aaebf1c44","author":{"name":"Matt Klein","email":"e2f3e9cbb1e558e519f4db318e95796b7ab57055@users.noreply.github.com"},"message":"client ssl filter: fix connection handling (#235)\n\nNow that we handle SSL client auth on a new connection (correct) we\r\nneed to wait until the handshake is complete before we do the auth\r\nchecks.","distinct":true,"url":"https://api.github.com/repos/amalgam8/envoy/commits/4090ba297aa76deea11b526f455c294aaebf1c44"},{"sha":"8d536670baac799b2f0a2c0147650e264e17dbec","author":{"name":"Matt Klein","email":"e2f3e9cbb1e558e519f4db318e95796b7ab57055@users.noreply.github.com"},"message":"network: fix double close event (#236)\n\nIt is theoretically possible that we complete the SSL handshake in\r\nthe write ready event. In this case, we may raise a connected event\r\nand have the connection closed. We need to handle this case and not\r\ndouble raise the event.","distinct":true,"url":"https://api.github.com/repos/amalgam8/envoy/commits/8d536670baac799b2f0a2c0147650e264e17dbec"}]}
{"actor":{"display_login":"rshriram"}}