Open mefellows opened 7 years ago
FWIW upgrading the json
gem from 1.8.6 to 2.1.0 removed this issue, I'm not sure if we can use that version of json though, I seem to recall there was a reason for not using 2+?
Interestingly, if I remove the 1.8.6
gem directory and let it use the default JSON library with the Ruby distribution (v1.8.1
), this test passes again (at least, it parses the JSON document which was the previous friction point).
Let's upgrade the json then, I'm pretty sure it's ok.
(Or rather, I can't remember it being an issue, guess we'll try and find out)
Looks like the restriction was coming from pact-provider-verifier. I'll put a new release out.
Cool - thanks! I'm in the process of going through updating stuff from the workshop and also those npm packages. Can look at this after
FWIW I pulled latest standalone, upgraded to latest verifier (bundle update
) and ran this test again - fixed it. Upgrading pact-go now...
Win
OK so something happened between that release and the latest published (1.3.1
at the time tested) where it came back, albeit with a different error:
With unicode chars: https://app.wercker.com/Pact-Foundation/pact-go/runs/build/598987263b92d9000169ec86?step=5989872cf250ac0001df5608
Without: https://app.wercker.com/Pact-Foundation/pact-go/runs/build/598985ff3b92d9000169eae7
Still investigating, this is just an update.
Getting an
Encoding::CompatibilityError
when running pact verification on Linux 64bit (consumer test is fine) with a pact containing unicode (chinese) characters. It also fails with emojis.Runtime details:
Note that I've tested this on OSX and it's not a problem.
Command:
Stack trace:
Pact file (matching_service-animal_profile_service.json):
See https://github.com/pact-foundation/pact-go/issues/41 for original issue.