Treating int64 as string when decoding with GRPC server reflection or GRPC proto file

[lyingcrow]

Expected Behavior

the .proto-message-field is int64 type. the number becomes number

Actual Behavior

the .proto-message-field is int64 type. the number becomes high {low} unsigned or string

Reproduction Steps

1. create a grpc request
2. choose GRPC server reflection or GRPC proto file
3. enter body ,click send
4. the Response body numbers will be displayed as strings

proto file as follows

syntax = "proto3";

package  test;

message TestRequest {
     int64 id =1;
}

message TestResponse {
     int64 code =1;
}
service TestServer {
     rpc process (TestRequest) returns (TestResponse)
}

Is there an existing issue for this?

• [X] I have searched the issue tracker for this problem.

Additional Information

relevant https://github.com/protobufjs/protobuf.js/issues/53

Insomnia Version

v2022.7.5

What operating system are you using?

Windows

Operating System Version

Windows 10 21H2

Installation method

insomnia.rest

Last Known Working Insomnia version

No response

[sajanv88]

I have this same result.

syntax = "proto3";

package token;

message Response { 
  int64 expiresIn = 1;
}

[1Bugivugi]

Same thing here

message TestDataStructure {
    uint64 qty = 1; 
    uint64 price = 2;
}

message TestResponse {
    repeated TestDataStructure ask = 1;
    ...
}

[ponder2000]

I am also facing the same issue

message ClientSubscriptionStatusResponse {
    string subscription_id = 1;
    string subscription_hash_id = 2;

    uint64 current_offset = 3;
    uint64 latest_offset = 4;
    uint64 lag = 5;

    bool is_online = 6;
    int64 lastConnectedOn = 7;
}

message ClientStatusResponse {
    string client_id = 1;
    repeated ClientSubscriptionStatusResponse subs = 2;
}

message ClientStatusListResponse {
    repeated ClientStatusResponse client = 1;
}