Skip to content
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

Upgrade websockets.legacy usage #16982

Open
cicdw opened this issue Feb 5, 2025 · 0 comments
Open

Upgrade websockets.legacy usage #16982

cicdw opened this issue Feb 5, 2025 · 0 comments
Labels
enhancement An improvement of an existing feature upstream dependency An upstream issue caused by a bug in one of our dependencies

Comments

@cicdw
Copy link
Member

cicdw commented Feb 5, 2025

Describe the current behavior

Currently we rely on imported objects from websockets.legacy which is deprecated (as can be seen here, for example: https://github.com/PrefectHQ/prefect/actions/runs/13147657643/job/36689175326?pr=16972).

Describe the proposed behavior

We need to plan to move to the newer asyncio implementation following the guidelines outlined here. We believe this should be straightforward as we don't rely on anything deep cut, but opening this issue to track so we don't get caught off guard with an upgrade.

Example Use

No response

Additional context

No response

@cicdw cicdw added enhancement An improvement of an existing feature upstream dependency An upstream issue caused by a bug in one of our dependencies labels Feb 5, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement An improvement of an existing feature upstream dependency An upstream issue caused by a bug in one of our dependencies
Projects
None yet
Development

No branches or pull requests

1 participant