Adam Rodger

I've added a test which reproduces the issue, and confirms that this is an issue in `pact-reference`, not `pact-net`. We're passing a string value but a numeric value ends up...

Unfortunately the upstream maintainers closed the linked issue I created to change this as they believe it's working as expected, and so there's nothing I can do to change this...

Nice, I'll give this a review later on 👍

I think this PR should be closed and an RFC raised with a proposed new API so we can discuss. Nobody likes pushing up a PR only to be told...

Yep, no problem. I saw the other issue, but just wanted to raise this one specifically because it's about the ANSI escapes rather than generally being incompatible. For me, once...

The actual cert I need to add is my company Root CA, because corporate firewalls intercept HTTPS, decrypt it and re-sign the stream with their own CA (a classic man...

I've recompiled `cargo-shuttle` locally with the `reqwest` feature `rustls-tls-native-roots` enabled, and I no longer get certificate errors because that will use the OS cert store instead of the built in...

I have this problem also - it's because the `TraceId` and `SpanId` fields are now top-level properties of `Serilog.Events.LogEvent` instead of key/value pairs inside the `Properties` collection, and this sink...

Currently there is no reliable way to detect libc vs musl during a .Net restore operation and therefore no reliable way to ensure the correct libpact binary is restored. That...

That's the design of the FFI packaging, so that the correct binary is restored to the bin folder when the NuGet is installed. That means we're leaning on existing features...