Open jkskj opened 1 month ago
Describe the bug
can access other service's method in multiple services
// kitexcall -idl-path idl/echo.proto -m One/Two -d '{}' -e 127.0.0.1:10001 // [Status]: Success // { // "message": "two" // }
message Request{ } message Response{ string message = 1; } service One { rpc One (Request) returns (Response) {} } service Two { rpc Two (Request) returns (Response) {} }
and fail using -transport TTHeader
// kitexcall -idl-path idl/echo.proto -m One/Two -d '{}' -e 127.0.0.1:10001 -transport TTHeader // [Status]: Failed // [ServerError]: RPC call failed: remote or network error: default codec read failed: EOF peer close
To Reproduce
Steps to reproduce the behavior:
kitexcall -idl-path idl/echo.proto -m One/Two -d '{}' -e 127.0.0.1:10001
Expected behavior
Screenshots
Kitex version:
v0.10.1
Environment:
Additional context
I also test other cases and record in https://github.com/jkskj/multiple/blob/main/main.go ,maybe useful for https://github.com/kitex-contrib/kitexcall/issues/7 and https://github.com/kitex-contrib/kitexcall/issues/8 .
Yes, currently it does not support multi service, it is in our plan if there are not many methods, it is recommended to define methods in one service
Describe the bug
can access other service's method in multiple services
and fail using -transport TTHeader
To Reproduce
Steps to reproduce the behavior:
kitexcall -idl-path idl/echo.proto -m One/Two -d '{}' -e 127.0.0.1:10001
Expected behavior
Screenshots
Kitex version:
v0.10.1
Environment:
Additional context
I also test other cases and record in https://github.com/jkskj/multiple/blob/main/main.go ,maybe useful for https://github.com/kitex-contrib/kitexcall/issues/7 and https://github.com/kitex-contrib/kitexcall/issues/8 .