That’s the same resultant binary. I don’t know if this represents a bug in the go sdk, or if something changed in the thrift. I’m not sure if there’s an easy way to sniff that socket