-
-
Notifications
You must be signed in to change notification settings - Fork 25
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
Test failures with trio >= 0.25.0
#187
Comments
It's due to the I'm not sure what to do, because Sure I can set |
I'm sorry but I don't really know trio to advise much but from what you're saying, I think you could duplicate tests to test with and without |
summary: trio-websocket is not "safe" to use with |
This is really about trio-websocket's support for trio nurseries always raising ExceptionGroup. The only reasonable way for packages and applications to deal with that is by using the new exception catching mechanism of The intention of the trio-websocket API has always been to avoid leaking concurrent exceptions (MultiError/ExceptionGroup, see #132). The most important thing is to preserve this behavior in the face of Managing this for the trio-websocket project might look like:
|
I just hit the same issue 🤔 |
py3-trio-websocket stopped working with py3-trio>=0.25. This broke the testsuite for streamlink. Delete til it is fixed upstream so we don't ship a broken package. ref: python-trio/trio-websocket#187
Delete the package til upstream has a solution. ref: python-trio/trio-websocket#187
Exception related tests fails with trio 0.25.0. Disable those til it is resolved upstream. ref: python-trio/trio-websocket#187
After upgrading to
trio >= 0.25.0
, the exception-related tests start failing:The text was updated successfully, but these errors were encountered: