Support for websockets==14.0 #14
Labels
enhancement
New feature or request
Comments
|
It appears that this is broken again in: Version 131.0.6778.70 (Official Build) (arm64) |
|
@therealpurplemana are you using |
|
Disregard. I rebooted and wiped my chrome data folder and it works fine.
…On Tue, Nov 12, 2024 at 2:18 PM Stephan Lensky ***@***.***> wrote:
@therealpurplemana <https://github.com/therealpurplemana> are you using
websockets==13.1? I'm pretty sure the previous issue wasn't related to
the Chrome version, it was just the websockets upgrade which caused it.
—
Reply to this email directly, view it on GitHub
<#14 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ATTERS6HWFNZCFCEFE267YT2AJ5B3AVCNFSM6AAAAABRTEAW2KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINZRGY4TONZVGI>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
|
This is fixed in the latest version, see https://github.com/stephanlensky/zendriver/releases/tag/v0.2.1 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The latest
websockets==14.0update has caused Zendriver to crash on browser start, see here: #12.For now, we have pinned an older version of
websockets, but we should fix the incompatibility so that we can upgrade to latest.The text was updated successfully, but these errors were encountered: