-
Notifications
You must be signed in to change notification settings - Fork 463
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Help debug message: "received EOF, stopping recv loop" #143
Comments
I also encountered this problem, It confused me And i just got the
|
the python side does not implement If someone could provide an example of how to do that on python that would be great |
I can't remember if we ever overcame this, but I think you'll want to make sure your grpc and protoc are updated to whatever TF is expecting here. |
@tzahifadida isn't the plugin the server and not the client? Does it need to implement that interface? |
Good day,
I'm working on a python plugin that I've been able to verify works as a grpc server to a python client, completely outside of the go-plugin framework.
The issue I'm running into is that before I make any calls against the plugin RPC service, I see the following warning.
However, I've no indication what method is being attempted to know what is not implemented. How can I debug this.
Also note, that even though I see this message, later in my code, I'm able to call the two RCP methods that I expect to work, and they do indeed return the desired results. I though this might be due to health checking against the python plugin, but I implemented it as written in the python example.
Can you give clues as to why this message is showing up or how to debug this? If code samples are required for understanding, I can provide some samples.
The text was updated successfully, but these errors were encountered: