<@U5FCZAAUU> trying to verify the protobuf enum fi...
# protobufs
j
@uglyog trying to verify the protobuf enum fix in 0.1.16 and hitting a non-obvious transport issue when i update to that version of the plugin. any tips on where to look or additional debug params to get more info on this?
Copy code
2022-11-15T19:24:42.769373Z ERROR ThreadId(01) pact_plugin_driver::content: Call to plugin failed - status: Unknown, message: "transport error", details: [], metadata: MetadataMap { headers: {} }
2022-11-15T19:24:42.769568Z ERROR ThreadId(01) pact_ffi::plugins: Failed to call out to plugin - Call to plugin failed - status: Unknown, message: "transport error", details: [], metadata: MetadataMap { headers: {} }
👋 1
u
Oh, damn. Someone else is also having some issues with that version. There may have been some updates to dependent libraries, let me investigate that.
🙌 1
y
Hey @Jason Taylor are you seeing this via Pact-Go? otherwise which client library are you using? I've been seeing the same issue in Go, and got the same issue in spike Ruby FFI application, if I have my logger enabled, https://github.com/pact-foundation/pact-reference/issues/230
j
@Yousaf Nabi (pactflow.io) yes - seeing in pact-go/v2/examples/grpc if using 0.1.16
u
Released 0.1.17 with a fix for the hanging plugin issue
j
looks good - tx!
🙌 1