grpc
"Unrecognized call object" exception thrown during runtime in grpc python asyncio service
What version of gRPC and what language are you using?
1.72.0
What operating system (Linux, Windows,...) and version?
Linux
What runtime / compiler are you using (e.g. python version or version of gcc)
Python 3.10.14
What did you do?
Start recently, after various dependency updates and code changes we start to see an exception thrown from here https://github.com/grpc/grpc/blob/v1.74.1/src/python/grpcio/grpc/aio/_channel.py#L435-L439 during regular asyncio channel usage inside an grpc python service (asyncio). The app has run grpc asyncio for quite a while this happens recently and intermittently.
Our team is trying to investigate too. We don't have a reproducible now. We wonder whether grpc core team has already an idea to this specific internal error, or could point us on how to debug further this issue.
What did you expect to see?
We don't expect to see this internal exception from happening.
What did you see instead?
exception thrown
grpc._cython.cygrpc.InternalError: Unrecognized call object: <grpc.aio._interceptor.StreamStreamCallResponseIterator object at 0x7090aa065810>:
at .intercept(/export/content/lid/apps/myapp/install/libexec/site-packages/grpc_interceptor/exception_to_status.py:192)
at .invoke_intercept_method(/export/content/lid/apps/myapp/install/libexec/site-packages/grpc_interceptor/server.py:165)
...
Make sure you include information that can help us debug (full error message, exception listing, stack trace, logs).
See TROUBLESHOOTING.md for how to diagnose problems better.
Anything else we should know about your project / environment?
Please let us know if you need more info that we can provide.
Hi @gillmylady , we had some fixes in recent versions, can you confirm if the issue is resolved in the latest version of gRPC.
Hi @gillmylady, thanks for clarifying. Please share the following information to investigate this further:
- What was the last version that worked for you without facing this issue?
- a repro case to locally reproduce the error
More than 30 days have passed since label "disposition/requires reporter action" was added. Closing this issue. Please feel free to re-open/create a new issue if this is still relevant.
No response to provide more information, so closing. More information can be provided and then we can reopen.
