[split] bump scrooge to 3.12.3-SNAPSHOT

RB_ID=271159
TBR=true
[split] util: fix announcing ipv6 wildcard address Systems with ipv6 enabled were announcing 0:0:0:0:0:0:0:0 since we only matched ipv4 wildcard address.

RB_ID=270487
[split] finagle-core: Fix race condition in server dispatcher draining state machine

RB_ID=267221
[split] finagle-core: Make `Resolver.evalLabeled` private[finagle]

RB_ID=271521
[split] finagle-core: low hanging fruit

RB_ID=266465
[split] Finagle: Use a more descriptive message for when client name resolution is negative

RB_ID=272625
[split] finagle-core: Users don't get NPE on directories without permissions

RB_ID=271887
[split] com.twitter.finagle.Stack: initial version

Stacks tackle the problem of constructing, transforming, and modifying
component stacks. You can think of Stack as a hybrid between a
component system, a narrowly-defined dependency injection system, and
a persistent datastructure.

This change uses Stacks to represent Finagle clients:
com.twitter.finagle.client.StackClient defines a template stack for a
codec to use -- it contains the full standard Finagle client stack,
and can be parameterized just like DefaultClient or ClientBuilders.

RB_ID=263207
[split] finagle-core: Remove a long-forgotten java file

RB_ID=271279
[split] finagle-doc: How do I change my timeouts in the Finagle 6 APIs?

RB_ID=267683
[split] finagle-tracing/zipkin: remove some allocations

RB_ID=272777
[split] Adds configbus/mirrord

RB_ID=268409
[split] finagle-core: Add a `ServerBuilder.safeBuild(ServiceFactory)` method for Java compatibility

RB_ID=271337
[split] Weights, weighted load balancer, memoization. (Deja-vu all over again.) Parts of this change list was already submitted, however it seems our submit queue dropped it on the floor. I took the opportunity to enhance the change a bit:

  1. add a flag for the default zk impl. of the serverset! resolver;
  2. add a flag for the default load balancer;
  3. memoize a few operations in the ZK facade.

The net effect of this is that we can have weighted load balancing,
with zk2 & the choice balancer without modifying any code. The
binary is launched with the flags:

  -com.twitter.server.serversetZkResolver=zk2
  -com.twitter.finagle.loadbalancer.defaultBalancer=choice

to enable these.

RB_ID=271027
[split] Revert "Weights, weighted load balancer, memoization. (Deja-vu all over again.)"

RB_ID=275011
TBR=true
NO-QUEUE=true
[split] Weights, weighted load balancer, memoization. (Deja-vu all over again.) Parts of this change list was already submitted, however it seems our submit queue dropped it on the floor. I took the opportunity to enhance the change a bit:

  1. add a flag for the default zk impl. of the serverset! resolver;
  2. add a flag for the default load balancer;
  3. memoize a few operations in the ZK facade.

The net effect of this is that we can have weighted load balancing,
with zk2 & the choice balancer without modifying any code. The
binary is launched with the flags:

  -com.twitter.server.serversetZkResolver=zk2
  -com.twitter.finagle.loadbalancer.defaultBalancer=choice

to enable these.

RB_ID=271027
[split] finagle-http: enable tracing on finagle 6 http api

RB_ID=270625
[split] finagle-core: Add basic Scaladocs for all Filters and Services

RB_ID=275101
[split]  Embeddable MySql support for Unit/Integration Testing in Finagle-MySql

RB_ID=267565
[split] make HttpDtab visible so we can call it in TFE

RB_ID=277035