Looks like you just need to refresh the server reflection. On Monday, November 18, 2024 at 10:45:15 AM UTC-5 Alexander Gelb wrote:
> I got this error also a lot of times. > Normally this happened when my request or response was not as expected > from the protocol buffer scheme. > Means that you are missing some elements or added to much elements or also > could be that you are not sending the right datatype. For me a lot of times > it happened, that I was sending integers, but my postman expected strings > (in arrays of ids for example). > > Maybe also check the proto buf on your client side, so it expects and > answers with the same version of your proto buf scheme. > > 신동찬 schrieb am Freitag, 15. November 2024 um 17:35:48 UTC+1: > >> i also got the same error when using postman - >> >> and for me the issue was that postman made the grpc request using >> outdated protobuf. >> >> i solved it by updating the protobuf postman refers to. >> On Thursday, August 29, 2024 at 2:33:44 AM UTC+9 Ishaan Kaustav wrote: >> >>> Is this issue resolved ? >>> we are getting the similar error , which says index out of bound in >>> response while sending http/2 request to the postman echo server . >>> >>> On Thursday 18 March 2021 at 08:53:49 UTC+5:30 Gaoyong Li wrote: >>> >>>> Thanks for your reply! >>>> This is my client code: >>>> [image: WechatIMG57.png] >>>> [image: WechatIMG56.png] >>>> After the error, I added the code to print the stack, but the error did >>>> not reappear. >>>> My client is a gateway service, and the gateway service parses the http >>>> request through the gin framework and calls the back-end grpc service. >>>> The GRPC request body is a bytes of json.The back-end grpc server >>>> parses the json body and deserializes it into the parameters of the grpc >>>> server interface by registering the json codec. >>>> [image: WechatIMG58.png] >>>> error message is "A weird issue index out of range: 3 + 116> 76". My >>>> request body is exactly 76 bytes, but I don't know what 3 and 116 are. >>>> At the time of the error, kubenetes also had no related logs. >>>> Now this error no longer appears, but I am very worried that it will >>>> appear in the live environment >>>> >>>> Please help me, thank you very much!!! >>>> >>>> On Thursday, March 18, 2021 at 1:58:02 AM UTC+8 Menghan Li wrote: >>>> >>>>> Can you provide more details of what the client/server do? >>>>> And maybe try to turn on logs: >>>>> https://github.com/grpc/grpc-go#how-to-turn-on-logging >>>>> And also check kubernetes error logs? >>>>> >>>>> It's not clear to me where the error is from. And this looks like a >>>>> recovered panic. >>>>> gRPC code doesn't use recover. Do you have recover in your code? Or it >>>>> might be the proxies? >>>>> >>>>> On Monday, March 15, 2021 at 2:07:20 AM UTC-7 a2640...@gmail.com >>>>> wrote: >>>>> >>>>>> Please see the FAQ in our main README.md before submitting your issue. >>>>>> I encountered a weird problem using grpc-go. An error is reported >>>>>> when calling the grpc interface, and the error message is "*Internal >>>>>> desc = index out of range: 3 + 116> 76*". Sometimes it is normal, >>>>>> sometimes an error is reported. >>>>>> >>>>>> My gateway application will parse the http request body and then call >>>>>> the remote rpc method. >>>>>> >>>>>> This is my request body,This is my request body, which is exactly 76 >>>>>> bytes >>>>>> >>>>>> [image: WechatIMG53.png] >>>>>> I have no problems running locally, but when I deploy the application >>>>>> to kubernetes, the above problems sometimes occur, but in most cases it >>>>>> works normally >>>>>> Under what circumstances will an error in this format appear? >>>>>> >>>>>> This is the version information of my dependency >>>>>> [image: WechatIMG54.png] >>>>>> >>>>>> Now I have no way to repeat the error. I worry about this in a live >>>>>> environment. >>>>>> >>>>>> Please help me. I'd appreciate it >>>>>> >>>>> -- You received this message because you are subscribed to the Google Groups "grpc.io" group. To unsubscribe from this group and stop receiving emails from it, send an email to grpc-io+unsubscr...@googlegroups.com. To view this discussion visit https://groups.google.com/d/msgid/grpc-io/2d54044d-f4e7-4cf7-b974-5f55a98cdedcn%40googlegroups.com.
