{"push_id":2887561815,"size":936,"distinct_size":1,"ref":"refs/heads/yg/travis-ci-troll","head":"57065858b4c6b7eb07e07eb91258898a22198044","before":"8cae980a535587ce14054175638998b014e1902c","commits":[{"sha":"7f4b052b10aac702d985d8288bf6c7afaec4e514","author":{"name":"Jillian Crossley","email":"deed3ca44874b93e1ee943b57059ab17d1a00b94@twitter.com"},"message":"finagle-memcached: Combine map/handle in ConnectedClient.rawGet\n\nProblem / Solution\n\nWe can save a function allocation in ConnectedClient.rawGet\nby combining `map`/`handle` in `transform`.\n\nRB_ID=917166","distinct":false,"url":"https://api.github.com/repos/twitter/finagle/commits/7f4b052b10aac702d985d8288bf6c7afaec4e514"},{"sha":"62261628a97f500ca258bccfa142f3a7ee37981a","author":{"name":"Jillian Crossley","email":"deed3ca44874b93e1ee943b57059ab17d1a00b94@twitter.com"},"message":"finagle-memcached: Remove intermediate Decoding representation when encoding\n\nProblem\n\nEncoding in the Finagle Memcached client has two steps;\nfirst, convert the `Command` to a `Decoding`, then write\nthat `Decoding` to a `Buf`. The intermediate `Decoding` representation\nmeans unnessecary object allocations.\n\nSolution\n\nOn the client side, encode `Command`s directly to `Buf`s. Before,\nboth the client and server used `Encoder` to encode `Decoding`s.\nNow, only the server uses it. Once the server also has its\nintermediate `Decoding` representation removed, the client and server\ncan have separate encoders, and `AbstractCommandToBuf` can be replaced\nby the client's encoder.\n\nRB_ID=917214","distinct":false,"url":"https://api.github.com/repos/twitter/finagle/commits/62261628a97f500ca258bccfa142f3a7ee37981a"},{"sha":"f47ffdfa1f67d1c029e5dc7d782e8d22de2d56a6","author":{"name":"Bryce Anderson","email":"a6cc2cef7d25f27847876bdb81651755fcebacf0@twitter.com"},"message":"finagle-memcached: optimize ParserUtil.split function\n\nProblem / Solution\n\nThe ParserUtils.split(data, delimiter) method is\nvery inefficient.\n\nRB_ID=917298","distinct":false,"url":"https://api.github.com/repos/twitter/finagle/commits/f47ffdfa1f67d1c029e5dc7d782e8d22de2d56a6"},{"sha":"2c3bdc832c9fdb637dd6ed9d49db904c554b5165","author":{"name":"Ruben Oanta","email":"772fe1f374d46bda4e68867185977c963227ef8e@twitter.com"},"message":"finagle-core: expire endpoints outside of aperture\n\nProblem\n\nEndpoints can fall out the aperture window and become idle.\nIn these cases, we would like to reclaim these resources.\n\nSolution\n\nImplement expiration on the Node type inside the Aperture load\nbalancer, which respects the aperture window. That is, nodes that\nbecome idle are only expired iff they are also outside the aperture\nwindow.\n\nWe set the idle time as a function of the aperture's smooth window.\nAperture changes are dampened by this window so after X windows\nhave passed, we can be sufficiently confident that an idle session\nis no longer needed. We choose a default of 10 for X which should\ngive us a high degree of confidence and, based on the default smooth\nwindows, should be on the order of minutes.\n\nResult\n\nThe number of active endpoints (and sessions in multiplexed protocols)\ncontinually converges towards the aperture size.\n\nRB_ID=916508","distinct":false,"url":"https://api.github.com/repos/twitter/finagle/commits/2c3bdc832c9fdb637dd6ed9d49db904c554b5165"},{"sha":"0bcd85ea359ebc4daafe41c766200e3cc88de583","author":{"name":"Jillian Crossley","email":"deed3ca44874b93e1ee943b57059ab17d1a00b94@twitter.com"},"message":"finagle-memcached: Don't create unnecessary Seqs when encoding\n\nProblem\n\nWhen encoding a command with associated data, we create\na Seq of 4 elements: name, key, flags, and expiry, and\niterate over this seq to encode each element. It's\nunnecessary to create this Seq.\n\nSolution\n\nSave an allocation by passing the name, key, flags, and expiry\nto the encoding function directly.\n\nRB_ID=917552\nTBR=true","distinct":false,"url":"https://api.github.com/repos/twitter/finagle/commits/0bcd85ea359ebc4daafe41c766200e3cc88de583"},{"sha":"b4cba227ef61185ff582419274dbf5be9f54aafb","author":{"name":"Jordan Parker","email":"7b85856224568f26fd9d01918b3ccf1defc1013b@twitter.com"},"message":"finagle-core: ServerAdmissionControl provides stack info to filter factories\n\nProblem\n\nAdmission control filters registered with the ServerAdmissionControl module are\nshared globally and cannot be configured on a per-server basis. There is no way\nto disable throttling AC via flag other than toggling. This makes it difficult\nto distinguish between a user explicitly disabling TAC no configuration.\n\nSolution\n\nHave the ServerAdmissionControl module register functions that create AC filters\ngiven parameters. This allows per-service control.\n\nRB_ID=917305","distinct":false,"url":"https://api.github.com/repos/twitter/finagle/commits/b4cba227ef61185ff582419274dbf5be9f54aafb"},{"sha":"832c95b7d3613a73aa4d98b1e651cc44859e78f1","author":{"name":"Yufan Gong","email":"af433595ea0b21d95b441b102956549931083147@twitter.com"},"message":"Bump sbt build from 2.11.8 to 2.11.11\n\nSummary: Problem/Solution:\n\nBump our sbt build crossScalaVersion to 2.11.11 since pants bumped theirs. Also,\nmove Finatra examples from 2.11.8 to 2.12.1.\n\nJIRA Issues: CSL-4555\n\nDifferential Revision: https://phabricator.twitter.biz/D56970","distinct":false,"url":"https://api.github.com/repos/twitter/finagle/commits/832c95b7d3613a73aa4d98b1e651cc44859e78f1"},{"sha":"3bab82eebed901d8562d71761ae6e468e2387777","author":{"name":"Ruben Oanta","email":"772fe1f374d46bda4e68867185977c963227ef8e@twitter.com"},"message":"finagle-core: ensure Aperture's expired counter is accurate\n\nProblem\n\nWe expire an endpoint and then we don't reset the `idleTime`.\nIn which case, on subsequent ticks of the expiry clock with no\nrequest activity, we will increment the `expired` counter while\n`remake` is a nop.\n\nSolution\n\nReset the `idleTime` to the sentinel value when we expire.\n\nRB_ID=917715","distinct":false,"url":"https://api.github.com/repos/twitter/finagle/commits/3bab82eebed901d8562d71761ae6e468e2387777"},{"sha":"1737d74178f998d0b3ec28538e9116615e0daea3","author":{"name":"Daniel Schobel","email":"afc5e40f7e0ce50d0caf1701580b337509dfc04f@twitter.com"},"message":"finagle-http: replace RespondToExpectContinue with HttpServerExpectContinueHandler\n\nSummary: Problem / Solution\n\nAfter upstreaming our RespondToExpectContinue handler to Netty we can\nremove Finagle's version.\n\nJIRA Issues: CSL-4168\n\nDifferential Revision: https://phabricator.twitter.biz/D58191","distinct":false,"url":"https://api.github.com/repos/twitter/finagle/commits/1737d74178f998d0b3ec28538e9116615e0daea3"},{"sha":"7317d448286ad145f7652a0df752d1a14172e164","author":{"name":"Jillian Crossley","email":"deed3ca44874b93e1ee943b57059ab17d1a00b94@twitter.com"},"message":"finagle-memcached: Remove intermediate Decoding in server encoding pipeline\n\nProblem\n\nEncoding in the Finagle Memcached server has two steps;\nfirst, convert the Response to a Decoding, then write\nthat Decoding to a Buf. The intermediate Decoding representation\nmeans unnessecary object allocations.\n\nSolution\n\nOn the server side, encode Responses directly to Bufs.\n\nRB_ID=917644","distinct":false,"url":"https://api.github.com/repos/twitter/finagle/commits/7317d448286ad145f7652a0df752d1a14172e164"},{"sha":"7f19e26888c86aa211d354aea2cd8074548710e5","author":{"name":"Daniel Schobel","email":"afc5e40f7e0ce50d0caf1701580b337509dfc04f@twitter.com"},"message":"finagle-mux: disable non-copying decoder for fragmenting clients\n\nSummary: Problem\n\nAggregating fragmented message payloads eliminates the performance\nbenefit of the non-copying decoder slicing along payload boundaries.\n\nSolution\n\nDisable it when message fragmention is configured.\n\nJIRA Issues: CSL-4670\n\nDifferential Revision: https://phabricator.twitter.biz/D58153","distinct":false,"url":"https://api.github.com/repos/twitter/finagle/commits/7f19e26888c86aa211d354aea2cd8074548710e5"},{"sha":"ece3e2188f28101583c2cbfe39bbd22537c249d3","author":{"name":"Moses Nakamura","email":"242df34e329d43994dd4cde92d05ccdc67ecc765@twitter.com"},"message":"finagle-http: Change default http implementation to netty4\n\nSummary: Problem\n\nWe have high confidence in the netty4 http implementation from running it in\nproduction for months, but we continue to use netty3 by default in OSS.\n\nSolution\n\nCut over to netty4 by default.\n\nResult\n\nOSS users of finagle will now use the netty4 http implementation by default.\n\nJIRA Issues: CSL-4703\n\nDifferential Revision: https://phabricator.twitter.biz/D58698","distinct":false,"url":"https://api.github.com/repos/twitter/finagle/commits/ece3e2188f28101583c2cbfe39bbd22537c249d3"},{"sha":"30bc64ec0504d9c8c6fb95850703dd3fa00e0a24","author":{"name":"Bryce Anderson","email":"a6cc2cef7d25f27847876bdb81651755fcebacf0@twitter.com"},"message":"finagle-mysql: BinaryEncodedRow should decode Int24 as mediumLE\n\nProblem / Solution\n\nFix a bug in the BinaryEncodedRow deserialization logic that reads 4\nbytes when decoding an Int24 instead of the required 3 bytes.\n\nRB_ID=917824","distinct":false,"url":"https://api.github.com/repos/twitter/finagle/commits/30bc64ec0504d9c8c6fb95850703dd3fa00e0a24"},{"sha":"09b32f85dbd3b0f4b5f93a1678f60f4ad79f8c2a","author":{"name":"Vladimir Kostyukov","email":"eff0e6b3b55c42f655c864be9b27028ce9b2d31b@twitter.com"},"message":"finagle-netty4: Remove poolReceiveBuffers toggle\n\nProblem / Solution\n\n`poolReceiveBuffers` toggle is suppressed by `UsePooling`. Remove the unused\ntoggle and its utilities.\n\nRB_ID=917912","distinct":false,"url":"https://api.github.com/repos/twitter/finagle/commits/09b32f85dbd3b0f4b5f93a1678f60f4ad79f8c2a"},{"sha":"a106faeea1a59ebd8b4f4ffbfb50fa92fa300f02","author":{"name":"Vladimir Kostyukov","email":"eff0e6b3b55c42f655c864be9b27028ce9b2d31b@twitter.com"},"message":"finagle-http: Remove UseNetty4 toggle\n\nProblem / Solution\n\nThere is no need for the UseNetty4 toggle. The migration is complete and we're removing\nthe toggle. Use `.configured(Http.Netty3Impl)` to switch the implementation over to Netty 3.\n\nRB_ID=917936","distinct":false,"url":"https://api.github.com/repos/twitter/finagle/commits/a106faeea1a59ebd8b4f4ffbfb50fa92fa300f02"},{"sha":"1e4252e305f03cba808ce635ff9d5837eb5e5404","author":{"name":"Masaru Nomura","email":"3aa4a972a3044f482de979dca6570755e078a013@gmail.com"},"message":"finagle-http: Remove body (and Content-Length) from 1xx, 204 and 304 responses\n\nProblem\n\nWe currently have two problems. Firstly, as described in RFC2616 and\nRFC7230, 1xx, 204 and 304 responses must not contain a message-body. This\nrequirement was not enforced in finagle, i.e., a message-body can be\nadded. Moreover, a Content-Length header field can be added to 1xx and\n204 responses, which is not allowed as mentioned in RFC7230#section-3.3.2.\n\nSolution\n\nFirstly, we have to clear a message-body, which we call content in finagle,\nif the response status code is either 1xx, 204 or 304 to satisfy RFC7230.\nThen, we need to remove a Content-Length header field in 1xx and 204 responses\nto follow RFC7230#section-3.3.2. With regard to a 304 response, we don't\nintentionally remove it even though a Content-Length header field is set.\n\nResult\n\nWe follow the specification of RFC with regard to a message-header and\nmessage-body except that we have not added some header fields required in a\nresponse with status code 304 to satisfy RFC7232#section-4.1; Any of the\nfollowing header fields must be generated: Cache-Control, Content-Location,\nDate, ETag, Expires, and Vary.\n\nSigned-off-by: Bryce Anderson <banderson@twitter.com>\n\nRB_ID=917827","distinct":false,"url":"https://api.github.com/repos/twitter/finagle/commits/1e4252e305f03cba808ce635ff9d5837eb5e5404"},{"sha":"4a19d7d0102a18b30bb04ddc8a8b94ea199d2e5f","author":{"name":"Bryce Anderson","email":"a6cc2cef7d25f27847876bdb81651755fcebacf0@twitter.com"},"message":"finagle-memcached: remove Decoding type from client decoder workflow\n\nProblem / Solution\n\nThe finagle-memcached client decoder pushes everything through an intermediate\n'Decoding' type which is unnecessary so we lift the transformation from tokens\nand data to protocol messages into the ClientDecoder type.\n\nRB_ID=917685","distinct":false,"url":"https://api.github.com/repos/twitter/finagle/commits/4a19d7d0102a18b30bb04ddc8a8b94ea199d2e5f"},{"sha":"5f6ea578c4a0f8385fe7c8a969022c8631bffff5","author":{"name":"Kevin Oliver","email":"24a54edd064a4908b8cc046e2ca1a8dcab73c61c@twitter.com"},"message":"finagle-doc: Spruce up request timeouts docs\n\nSummary: Problem\n\nThe docs on request timeouts could use a little sprucing up.\n\nSolution\n\nSpruce them.\n\nJIRA Issues: csl-3880\n\nDifferential Revision: https://phabricator.twitter.biz/D59280","distinct":false,"url":"https://api.github.com/repos/twitter/finagle/commits/5f6ea578c4a0f8385fe7c8a969022c8631bffff5"},{"sha":"fadc80cdd804f2885ebc213964542d5568a4f485","author":{"name":"Ruben Oanta","email":"772fe1f374d46bda4e68867185977c963227ef8e@twitter.com"},"message":"csl: June Release\n\nSummary: Problem\n\nWe want to release the next versions of our Twitter OSS libraries:\n - util -> 6.45.0\n - scrooge -> 4.18.0\n - finagle -> 6.45.0\n - twitter-server -> 1.30.0\n - finatra -> 2.11.0\n\nSolution\n\nPrepare libraries for their next releases.\n\nDifferential Revision: https://phabricator.twitter.biz/D59353","distinct":false,"url":"https://api.github.com/repos/twitter/finagle/commits/fadc80cdd804f2885ebc213964542d5568a4f485"},{"sha":"e8832609b080f1e495851ea8a9bb5b0b9e2394a3","author":{"name":"Moses Nakamura","email":"242df34e329d43994dd4cde92d05ccdc67ecc765@twitter.com"},"message":"finagle-netty4: Support passing a chain file for mutual authentication\n\nSummary: Problem\n\nIt's impossible to pass a chain file to the client, so the server needs to pass\nthe intermediate certificates if it wants the client to recognize a root that it\ntrusts through an intermediate certificate.\n\nSolution\n\nAdd support for the CertKeyAndChain API in netty 4, which makes it possible to\npass a chain file to the client.\n\nJIRA Issues: CSL-4686\n\nDifferential Revision: https://phabricator.twitter.biz/D59531","distinct":false,"url":"https://api.github.com/repos/twitter/finagle/commits/e8832609b080f1e495851ea8a9bb5b0b9e2394a3"}]}
{"actor":{"display_login":"yufangong"}}