Stanislav Vodetskyi
01/26/2024, 2:09 AMfalse
in that field (i can adjust the state in the test), I'm getting this error from the protobuf plugin:
1) Verifying a pact between <consumer> and <provider> - <message>
2024-01-25 17:53:27.1661 ┃ 1.1) has a matching body
2024-01-25 17:53:27.1661 ┃ $ -> Expected message '<message>' but was missing or empty
This happens regardless of whether consumer expects true or false. The server seems to respond with a correct message, seeing how changing the state to return true
makes the plugin work correctly, passing if the consumer requested true and failing if the consumer requested false.
This could be because boolean false is default, so the plugin cannot distinguish empty response from the explicit false, or am I misreading this?Stanislav Vodetskyi
01/26/2024, 2:13 AMdecode_message
returns empty for such a proto, here:
https://github.com/pactflow/pact-protobuf-plugin/blob/main/src/message_decoder/mod.rs#L258
2024-01-26T01:32:33.300435Z INFO tokio-runtime-worker request{method=POST uri=<http://127.0.0.1:57435/io.pact.plugin.PactPlugin/VerifyInteraction> version=HTTP/2.0 headers={"te": "trailers", "content-type": "application/grpc", "authorization": Sensitive, "user-agent": "tonic/0.9.2"}}:decode_message: pact_protobuf_plugin::message_decoder: return=Ok([])
rholshausen
01/28/2024, 10:29 PMrholshausen
01/28/2024, 10:29 PMrholshausen
01/29/2024, 6:17 AM