Adam Rodger

Do we know if this was fixed? I'm getting a lot of requests to release PactNet 5.0 fully and this is a blocking issue for the full release.

I've upgraded to FFI 0.4.23 and can confirm this issue is no longer happening 👍

Any option we choose I'd like the escape hatch of always allowing the user to override it. There'll be times when the detection just gets it wrong. There'll be times...

Yeah I much prefer the default to be that the user specifies the content type, and an opt-in option for auto detection. At least then when auto detection gets it...

How does that work in terms of the spec though? Unless the spec can define what will happen during that auto detection then the spec becomes ambiguous. If the behaviour...

I'm not really sure if that's the right thing to do...? Anything that said it was V3 compliant before has now been made retrospectively non-compliant. Shouldn't we issue new spec...

Perhaps I've not got my point across properly there. What I'm saying is that you can't modify the spec according to what the reference implementation does. Specs are supposed to...

First thing to try is making sure that solution works outside of a dev container. If it does then the problem must be something within the dev container itself. If...

Closed due to inactivity

It's been school holidays so I've been on vacation and I'm a bit behind. I'll review this properly tomorrow when I'm not on my phone, but my initial observations are:...