-
Notifications
You must be signed in to change notification settings - Fork 34
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
Encoding::CompatibilityError on Linux 64bit #5
Comments
FWIW upgrading the |
Interestingly, if I remove the |
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 ( |
Win |
OK so something happened between that release and the latest published ( 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:
See contract doesn't support chinese pact-go#41
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 pact-foundation/pact-go#41 for original issue.
The text was updated successfully, but these errors were encountered: