-
Notifications
You must be signed in to change notification settings - Fork 10
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
Tests fail (with Protocol::WebSocket 0.22?) #33
Comments
Indeed, these changes are likely the trigger: |
Sorry, blame @leonerd for that :) |
Oops. This is almost certainly related to Unicode string vs. UTF-8 character handling in the surrounding code. If someone can give me a bit of hand-holding about development/setup/testing on this code I'll be happy to take a look and see if I can fix it. |
Oh actually it's a ~2line patch to fix. You may need to bump the version requirement of Clarification: It shouldn't need |
Thanks for the speedy fix. We already require |
Patch seems to work with |
It effected other modules that's why I reverted it for now. |
yeah. I gathered. I've released this fix as WSC |
I will try to make sure dependent modules keep working %)
…On Dec 12, 2017 21:43, "✈ Graham ✈" ***@***.***> wrote:
yeah. I gathered.
I've released this fix as WSC 0.44, as it fixes compat with PW 0.22 and
doesn't seem to break any of the other versions that we support. Please let
me know if there are any changes in WSC required for good fix referred to
here: vti/protocol-websocket#54 (comment)
<vti/protocol-websocket#54 (comment)>
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#33 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAB6M4tEvilnGTOMYGBAfhFDkouUCsHNks5s_uV4gaJpZM4Q8Zzr>
.
|
Tests started to fail on my smokers:
Statistical analysis suggests that the problem started with Protocol::WebSocket 0.22 (@vti @leonerd: FYI):
The text was updated successfully, but these errors were encountered: