{"push_id":1212426478,"size":1,"distinct_size":1,"ref":"refs/heads/remote_hp_mismatch","head":"572df66e31b5f624958f2533288b5f43d9b48b07","before":"8d1002413713829845101d85b3dde1e5f97788cb","commits":[{"sha":"572df66e31b5f624958f2533288b5f43d9b48b07","author":{"name":"Prashant Varanasi","email":"11e7a890529a76e490b6b424f1e54fdbb430b978@uber.com"},"message":"Handle host:port mismatches between peer.Connect and remote peer\n\nCurrently, if we conect to peer as \"a:1\" and it sends us an init req\nheader with host:port set to \"b:2\", we only add it under the peer \"b:2\".\n\nAfter this change, the connection will be added under both peers so that\nfuture calls to \"a:1\" will be able to use the same connection.\n\nWhen this happens, we log the host:port mismatch under a debug log.\nIn future, we may want to emit metrics when this happens.\n\nThis information (outboundHostPort vs remoteHostPort) is also exposed\nvia introspection.","distinct":true,"url":"https://api.github.com/repos/uber/tchannel-go/commits/572df66e31b5f624958f2533288b5f43d9b48b07"}]}
{"actor":{"display_login":"prashantv"}}