-
Notifications
You must be signed in to change notification settings - Fork 30
Wrong protobuf type in ClusterControllerClient.diagnose_cluster #51
Comments
@tseaver @busunkim96 would you mind taking a look? I can help to solve it but would like to be sure that real bug not only me :) |
@bradmiro Could you take a look? @turbaszek Did this behavior start recently? |
It's the first time I used this functionality so I cannot help here |
Thanks @turbaszek for raising this, I was able to reproduce this in a non-Airflow environment as well. I'll take a look. This issue appears to go as far back as at least 0.7.0 (I didn't test earlier versions than this). |
Thanks @bradmiro ! |
The trace is very similar googleapis/google-cloud-python#9150, so perhaps this is the same issue? I no longer remember how that was resolved, so I'll need to dig through my email a bit more. |
I think the cause is a mismatch between the annotated response/metadata type for this LRO and what is returned by the API https://github.com/googleapis/googleapis/blob/a7ed6d42ebf4f4b9862c94e096d37aef92728212/google/cloud/dataproc/v1/clusters.proto#L100-L118 Opened internal PR 321053288. |
A Dataproc engineer confirmed that the current annotation is incorrect. This should be fixed once the library is regenerated with the tweaked protos. Lowering the priority since this only prevents retrieval of the response object. ETA for a new release is by the end of this week. |
Thanks @busunkim96! |
Thank you @busunkim96 ! |
Environment details
pip --version
google-cloud-dataproc
version: 1.0.0Steps to reproduce
diagnose_cluster
on the cluster.result()
to wait for the operation to completeCode example
Stack trace
I tried to debug this code and use
google.protobuf.any_pb2.Any
but then I getTypeError: Could not convert Any to Any
.The text was updated successfully, but these errors were encountered: