-
Notifications
You must be signed in to change notification settings - Fork 70
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
Certain input causes mock service to hang #7
Comments
Bizarre, haven't had that before. One thing to look at is that it uses JSON.load(because sometimes there are embedded Ruby classes eg. Pact::Term) not JSON.parse. |
Any news on this one? |
Hi @bethesque - reviving an old thread here. I've noticed that this is still happening when using matchers that generate a regex pattern. I've been using the PHP Pact library and using matchers such as I noticed when trying to send a curl request once it has hanged, I receive a connection refused so it is like the service has entered an unhealthy state. What is really interesting is that this has only happened since I have hit a larger number of pacts (I have ~26 pacts to verify against now). When I remove any one of these, it seems to run ok again. However, when I have replaced these regex matchers with the |
The uuid and dateTimeISO8601 aren't natively supported, so they must be wrappers for "terms" provided by the pact php library. Can you see if you can recreate it using https://github.com/pact-foundation/pact-ruby-standalone-e2e-example ? |
I'll investigate this further later, reporting so not to lose track of this bug.
When setting an expected interaction response with the following body payload, and posting to PACT, the server hangs until HTTP timeout.
Removing the regular expressions from the payload avoids the problem.
The text was updated successfully, but these errors were encountered: