Int64 support about bloomrpc HOT 5 CLOSED

This take effect, thanks a lot. But there another annoying case appear.
My request is

{
  "uids": [
    "2569253357013176641"
  ]
}

while the response is

{
  "user_map": {
    "A\u0011ÀÒPÒ§#": {
      "uid": "2569253357013176641",
      "nick_name": "刘勇#41793",
      "user_icon": "https://icdn.rightpaddle.net/user_icon/2569253357013176641-21B8E06234BF40B4AEA436415821928E.jpg",
      "signature": "",
      "user_role": "0",
      "status": 1,
      "sex": 1,
      "type": 1,
      "risk_state": 0
    }
  }
}

the response user_map's key should be int64 or int64 string of id in request, but in this case, it looks messy, so there is something I can do to solve this.

from bloomrpc.

Try passing the parameter as a string instead of a number i think protobuf will handle the parsing of the int64 internally

from bloomrpc.

@leaxoy mmmh, this is interesting... I've done a bit of digging on this and it looks like grpc-node doesn't unserialise correctly int64 when defined on a map key, I'd be suggesting to open an issue on their repo https://github.com/grpc/grpc-node/issues and see what they say

from bloomrpc.

Please can you file an issue in grpc-node and open an new issue once upstream is resolved

from bloomrpc.

maybe you can try https://github.com/crossoverJie/ptg

from bloomrpc.