{"push_id":2381253692,"size":15,"distinct_size":0,"ref":"refs/heads/master","head":"5f5dee4791a41fd814f6c6a2f574a6fb77e811d0","before":"d0a9138c66b0b8d2d622bd8584dd411e1a11ce6a","commits":[{"sha":"3c5860484014c33210ff19f58f9491c3e0e0db80","author":{"name":"Yufan Gong","email":"9ffe62c94d83df46a5e0b4debf32c30eacd9a066@twitter.com"},"message":"Twitter-oss: Updtae OSS libraries post release to 18.3.0-SNASHOT\n\nSummary: Problem\n\nWe want to update the next version of our Twitter OSS libraries 18.3.0-SNAPSHOT\n\n  - util\n  - scrooge\n  - finagle\n  - twitter-server\n  - finatra\n\nSolution\n\nUpdate the libraries post release.\n\nDifferential Revision: https://phabricator.twitter.biz/D134961","distinct":false,"url":"https://api.github.com/repos/twitter/util/commits/3c5860484014c33210ff19f58f9491c3e0e0db80"},{"sha":"b9a54a932b95f2d14346fbc3de1c451f2b4c1ea2","author":{"name":"Vladimir Kostyukov","email":"52df49c4d0499e5c7ba54f155067516e77e6feba@twitter.com"},"message":"util-benchmarks: Improving Future.respond benchmark\n\nSummary: # Problem / Solution\n\nThe chained future returned form `Promise.respond` was stack-allocated\n(possibly, even eliminated as dead code). We want to account for it in our\nbenchmark so we return it as a result instead of swallowing it.\n\nJIRA Issues: CSL-5816\n\nDifferential Revision: https://phabricator.twitter.biz/D136676","distinct":false,"url":"https://api.github.com/repos/twitter/util/commits/b9a54a932b95f2d14346fbc3de1c451f2b4c1ea2"},{"sha":"31efdaf028dc5788821822680cf28924ed6a0524","author":{"name":"Christopher Coco","email":"73f81dcde656bf14f3aba707425184e601614d53@twitter.com"},"message":"util-app: Ensure flag parsing error reason is emitted before printing Flags#usage\n\nSummary: Problem\n\nCurrently when flag parsing fails we attempt to concatenate the reason for the\nfailure (i.e., which flag input failed to be parsed) with the result of\n`Flags#usage` which collects and prints all available flags to be set. The\nissue is that collecting the flag usage can be an expensive operation in that\nthe code attempts to scan the entire classpath for all global flags. This can\nfail in some situations (with an OOM) due to the application having a fairly\nlarge classpath.\n\nSolution\n\nWe want to ensure that users get the error reason before attempting to collect\nand print all available flags of the system, thus we break out calling\n`Flags#usage` from the error reason and delay the invocation until after we\nhave printed (and flushed) the error reason to System.err.\n\nNote:\n\nThese changes do not attempt to solve the problem of an application running into\nan OOM when `Flag#usage` fails due to a large classpath. It only attempts to\nactually provide the useful error reason regardless of the OOM happening.\n\nJIRA Issues: CSL-5597\n\nTBR=true\n\nDifferential Revision: https://phabricator.twitter.biz/D137629","distinct":false,"url":"https://api.github.com/repos/twitter/util/commits/31efdaf028dc5788821822680cf28924ed6a0524"},{"sha":"0e27f594a510e82555e2a66809d33a2466b0829c","author":{"name":"Vladimir Kostyukov","email":"52df49c4d0499e5c7ba54f155067516e77e6feba@twitter.com"},"message":"util-core: Deprecate RichU64* APIs\n\nSummary: # Problem / Solution\n\nJava 8 comes with the new APIs for unsigned longs, which also is 10x faster than RichU64*.\nWe're deprecating `RichU64String`, `RichU64Long`, and `RichU64ByteArray` in favor of\nJava 8 API.\n\nJIRA Issues: CSL-5689\n\nDifferential Revision: https://phabricator.twitter.biz/D137893","distinct":false,"url":"https://api.github.com/repos/twitter/util/commits/0e27f594a510e82555e2a66809d33a2466b0829c"},{"sha":"1d4f0ca688329fdc7d05bfe483715fadfdf9de2c","author":{"name":"Shane Delmore","email":"1bddd3270aa35caba3c276b5d6c7ede2608105fc@twitter.com"},"message":"Remove unused imports from scala file using Scalafix\n\nSummary: This is the result of running Scalafix rule RemoveUnusedImports against source\n\nDifferential Revision: https://phabricator.twitter.biz/D139088","distinct":false,"url":"https://api.github.com/repos/twitter/util/commits/1d4f0ca688329fdc7d05bfe483715fadfdf9de2c"},{"sha":"bd44f38651637c075564f3ab3fd026d6f9c4a1ae","author":{"name":"Daniel Wagner-Hall","email":"36fc4dce209202f40d2cc7d79e7cc241f25a28e7@twitter.com"},"message":"Format all remaining BUILD files with buildifier\n\nSummary: If you are finding it hard to rebase past this commit, try running:\n`curl https://cgit.twitter.biz/source/plain/devprod/linting/scripts/rebase_past_build_formatting.sh | bash`\n\nThis also enables the auto-fix linter for all files.\n\nSee go/buildifier for more information.\n\nIf you run into any problems, or need any help, please file a ticket\nunder DPB or email build@.\n\nJIRA Issues: DPB-9555\n\nTBR=true\n\nDifferential Revision: https://phabricator.twitter.biz/D139669","distinct":false,"url":"https://api.github.com/repos/twitter/util/commits/bd44f38651637c075564f3ab3fd026d6f9c4a1ae"},{"sha":"b8b0e5ce370adfdcf1b44813903b0e7a6475ab83","author":{"name":"Jillian Crossley","email":"fd125a3f42048646810c0f929f29edd9f84d7bfe@twitter.com"},"message":"Remove jillianc from CSL owners files\n\nSummary: Problem / Solution\n\njillianc is no longer part of CSL and should be removed\nfrom the relevant OWNERS files. *sadness*\n\nDifferential Revision: https://phabricator.twitter.biz/D139910","distinct":false,"url":"https://api.github.com/repos/twitter/util/commits/b8b0e5ce370adfdcf1b44813903b0e7a6475ab83"},{"sha":"bf47b55ff45a31bbd541f66257f2244df5c35f5b","author":{"name":"Vladimir Kostyukov","email":"52df49c4d0499e5c7ba54f155067516e77e6feba@twitter.com"},"message":"util-core: Remove UseLifo toggle and switch Twitter Futures to LIFO\n\nSummary: # Problem / Solution\n\nTwitter Futures now use LIFO callback execution order.\n\nJIRA Issues: CSL-5816\n\nDifferential Revision: https://phabricator.twitter.biz/D135407","distinct":false,"url":"https://api.github.com/repos/twitter/util/commits/bf47b55ff45a31bbd541f66257f2244df5c35f5b"},{"sha":"753b3644f1821b62f19ec7faaddfaf17405620ef","author":{"name":"Stefan Lance","email":"da7005da67c40af49df0eb94d3b8dfa057b13478@twitter.com"},"message":"finagle, util: Add benchmarks to measure `Buf.concat`\n\nSummary: Problem\n\nWe would like more insight into how `Buf.concat` performs.\n\nSolution\n\nAdd benchmarks to measure `Buf.concat` for small `Composite`s, and split up\nthe Mux Message benchmarks so we can measure `Buf.concat` in just the encode\ncode path.\n\nJIRA Issues: CSL-6080\n\nDifferential Revision: https://phabricator.twitter.biz/D141516","distinct":false,"url":"https://api.github.com/repos/twitter/util/commits/753b3644f1821b62f19ec7faaddfaf17405620ef"},{"sha":"060a8d15bd5a3c9121e71ea3f9a1fb9974d4ab6f","author":{"name":"Stefan Lance","email":"da7005da67c40af49df0eb94d3b8dfa057b13478@twitter.com"},"message":"util-core: Optimize `Buf.concat`\n\nSummary: Problem\n\nConcatenating two `Buf`s creates a `Composite`, which stores its\nunderlying `Buf`s in a `Vector`. Allocating this `Vector` is relatively\nexpensive.\n\nSolution\n\nWhen the `Composite` is made of two or three `Buf`s, optimize its\nimplementation by storing the underlying `Buf`s in specialized\nimplementations of `IndexedSeq` with minimal overhead.\n\nResult\n\n`Buf.concat` is faster and allocates less space.\n\nJIRA Issues: CSL-6081\n\nDifferential Revision: https://phabricator.twitter.biz/D141535","distinct":false,"url":"https://api.github.com/repos/twitter/util/commits/060a8d15bd5a3c9121e71ea3f9a1fb9974d4ab6f"},{"sha":"63d1caf3b86044f6fe8ba7fd02be41d549350800","author":{"name":"Christopher Coco","email":"73f81dcde656bf14f3aba707425184e601614d53@twitter.com"},"message":"util-core: Wrap the function passed to `c.t.util.Closable.make` in a try/catch\n\nSummary: Problem\n\nThe function passed to `c.t.util.Closable.make` is expected to return a\n`Future[Unit]` but we do not properly protect against the situation where\nthe function throws a non fatal exception. Any thrown non fatal should get\ntransformed into a failed Future.\n\nSolution\n\nWrap the passed function with a try/catch where any caught NonFatal exception\nis translated to a `Future.exception`.\n\nResult\n\nCode that potentially throws a non fatal gets correctly translated to a\nfailed Future instead of having the non fatal propagated back up the stack.\n\nJIRA Issues: CSL-6098\n\nDifferential Revision: https://phabricator.twitter.biz/D142086","distinct":false,"url":"https://api.github.com/repos/twitter/util/commits/63d1caf3b86044f6fe8ba7fd02be41d549350800"},{"sha":"c10da8e53179c5f8c9b105f919b7639985f4594a","author":{"name":"Vladimir Kostyukov","email":"52df49c4d0499e5c7ba54f155067516e77e6feba@twitter.com"},"message":"util-core: Fix race condition in Var.async\n\nSummary: Problem / Soltuion\n\nThere is a race condition between `closable` and `observe` in `Var.async` as they synchronize\non different monitors. The `closable` instance synchronizes on closure's (i.e., `Function` monitor),\nwhile `observe` on var's own monitor.\n\nJIRA Issues: CSL-6079\n\nDifferential Revision: https://phabricator.twitter.biz/D142478","distinct":false,"url":"https://api.github.com/repos/twitter/util/commits/c10da8e53179c5f8c9b105f919b7639985f4594a"},{"sha":"e0f9d431868ef5fc7f4cad7c4d2269f3f10b011e","author":{"name":"Kevin Oliver","email":"42f0c465f9d28c5edb4e65e73bb0815be7cdcaf5@twitter.com"},"message":"util/doc: Add section on useful StatsReceivers\n\nSummary: Problem\n\nSome useful StatsReceivers are not well known.\n\nSolution\n\nCall them out in the util-stats docs.\n\nJIRA Issues: csl-4917\n\nDifferential Revision: https://phabricator.twitter.biz/D142619","distinct":false,"url":"https://api.github.com/repos/twitter/util/commits/e0f9d431868ef5fc7f4cad7c4d2269f3f10b011e"},{"sha":"d4f8051ea4ba8baad22bd54e23d2ffda2340b2f6","author":{"name":"Kevin Oliver","email":"42f0c465f9d28c5edb4e65e73bb0815be7cdcaf5@twitter.com"},"message":"util/doc: Document full histogram details\n\nSummary: Problem / Solution\n\nWhile we have a section about finagle-stats, we do\nnot mention that users can see the full histogram\ndetails on the /admin/histogram admin page.\n\nJIRA Issues: csl-2945\n\nDifferential Revision: https://phabricator.twitter.biz/D143293","distinct":false,"url":"https://api.github.com/repos/twitter/util/commits/d4f8051ea4ba8baad22bd54e23d2ffda2340b2f6"},{"sha":"5f5dee4791a41fd814f6c6a2f574a6fb77e811d0","author":{"name":"Stefan Lance","email":"da7005da67c40af49df0eb94d3b8dfa057b13478@twitter.com"},"message":"twitter-oss: Prepare OSS libraries for release 18.3.0\n\nSummary: Problem\n\nWe want to release the next versions of our Twitter OSS libraries 18.3.0\n - util\n - scrooge\n - finagle\n - twitter-server\n - finatra\n\nSolution\n\nPrepare libraries for their next releases.\n\nJIRA Issues: CSL-6115\n\nTBR=true\n\nDifferential Revision: https://phabricator.twitter.biz/D144231","distinct":false,"url":"https://api.github.com/repos/twitter/util/commits/5f5dee4791a41fd814f6c6a2f574a6fb77e811d0"}]}
{"actor":{"display_login":"finaglehelper"}}