-
Notifications
You must be signed in to change notification settings - Fork 46
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
Verifier Results with empty notices #404
Comments
Just make the step a no-op as the underlying Rust code will emit the warning. |
Cool, I'll make this a no-op. |
JP-Ellis
added a commit
to pact-foundation/pact-python
that referenced
this issue
Mar 20, 2024
Following recommendations from Ron, making the check a no-op. Ref: pact-foundation/pact-reference#404 Signed-off-by: JP-Ellis <[email protected]>
JP-Ellis
added a commit
to pact-foundation/pact-python
that referenced
this issue
Mar 22, 2024
Following recommendations from Ron, making the check a no-op. Ref: pact-foundation/pact-reference#404 Signed-off-by: JP-Ellis <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When implementing the compatibility suite, I came across the following scenario (ref)
It requires checking that a warning is displayed, which to my knowledge, is difficult to do through the FFI. When logging is enabled, the FFI does emit the correct warning:
However inspecting the logs requires logging to a buffer, and would fail if logging to
stderr
is configured for example.Inspecting the verifier results, there is a
notices
key, though it appears to be empty:and I am left wondering whether this is an error with the FFI or not.
The text was updated successfully, but these errors were encountered: