Pact test give an "API handler start failed" error while test is successful

[BenDurmishllariEP]

Expected behaviour

Successful PASS without seeing any unrelated error

Actual behaviour

Successful PASS with seeing an unrelated error - For e.g [ERROR] API handler start failed: accept tcp [::]:37875: use of closed network connection

Steps to reproduce

Use a pact v1.6.7, it seems that the issue came from this change: https://github.com/pact-foundation/pact-go/commit/01b8e81055963c2cb0e40d449a72662a3c98aadf

[mefellows]

Thanks.

It would be great to get actual repro steps - e.g. a GH actions build that shows this, and the specific configuration you have leading to that behaviour.

It could be something specific to certain environments (e.g. it looks like an IPv6 issue, and perhaps that's not allowed in your env).

[dlouwers]

Hi,

I am having a similar issue ([ERROR] API handler start failed: accept tcp [::]:) using pact 1.7.0. I am willing to try and reproduce it in isolation but would first like to know if pact-go requires ipv6 support and in what way exactly. Because if it does I'd rather try to approach a fix from that direction first.

Kind regards.