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

Support strict_exception_groups=True #188

Merged
merged 10 commits into from
Sep 21, 2024
2 changes: 1 addition & 1 deletion .github/workflows/ci.yml
Original file line number Diff line number Diff line change
Expand Up @@ -74,7 +74,7 @@ jobs:
strategy:
matrix:
os: [ubuntu-latest]
python-version: ['3.12']
python-version: ['3.13-dev']
steps:
- uses: actions/checkout@v3
- name: Setup Python
Expand Down
5 changes: 2 additions & 3 deletions requirements-dev-full.txt
Original file line number Diff line number Diff line change
Expand Up @@ -21,7 +21,7 @@ build==1.2.1
# via pip-tools
certifi==2024.6.2
# via requests
cffi==1.16.0
cffi==1.17.0
# via cryptography
charset-normalizer==3.3.2
# via requests
Expand Down Expand Up @@ -194,9 +194,8 @@ tomli==2.0.1
# pytest
tomlkit==0.12.5
# via pylint
trio==0.24.0
trio==0.25.1
# via
# -r requirements-dev.in
# pytest-trio
# trio-websocket (setup.py)
trustme==1.1.0
Expand Down
1 change: 0 additions & 1 deletion requirements-dev.in
Original file line number Diff line number Diff line change
Expand Up @@ -4,5 +4,4 @@ pip-tools>=5.5.0
pytest>=4.6
pytest-cov
pytest-trio>=0.5.0
trio<0.25
trustme
3 changes: 1 addition & 2 deletions requirements-dev.txt
Original file line number Diff line number Diff line change
Expand Up @@ -71,9 +71,8 @@ tomli==2.0.1
# coverage
# pip-tools
# pytest
trio==0.24.0
trio==0.25.1
# via
# -r requirements-dev.in
# pytest-trio
# trio-websocket (setup.py)
trustme==1.1.0
Expand Down
1 change: 1 addition & 0 deletions requirements-extras.in
Original file line number Diff line number Diff line change
@@ -1,6 +1,7 @@
# requirements for `make lint/docs/publish`
mypy
pylint
mypy
jakkdl marked this conversation as resolved.
Show resolved Hide resolved
sphinx
sphinxcontrib-trio
sphinx_rtd_theme
Expand Down
121 changes: 120 additions & 1 deletion tests/test_connection.py
Original file line number Diff line number Diff line change
Expand Up @@ -32,7 +32,9 @@
from __future__ import annotations

from functools import partial, wraps
import re
import ssl
import sys
from unittest.mock import patch

import attr
Expand All @@ -48,6 +50,13 @@
except ImportError:
from trio.hazmat import current_task # type: ignore # pylint: disable=ungrouped-imports


# only available on trio>=0.25, we don't use it when testing lower versions
try:
from trio.testing import RaisesGroup
except ImportError:
pass

from trio_websocket import (
connect_websocket,
connect_websocket_url,
Expand All @@ -60,12 +69,23 @@
open_websocket,
open_websocket_url,
serve_websocket,
WebSocketConnection,
WebSocketServer,
WebSocketRequest,
wrap_client_stream,
wrap_server_stream
)

from trio_websocket._impl import _TRIO_MULTI_ERROR

if sys.version_info < (3, 11):
from exceptiongroup import BaseExceptionGroup # pylint: disable=redefined-builtin

if _TRIO_MULTI_ERROR:
EXCEPTION_GROUP_TYPE = trio.MultiError # type: ignore[attr-defined] # pylint: disable=no-member
else:
EXCEPTION_GROUP_TYPE = BaseExceptionGroup # pylint: disable=possibly-used-before-assignment

WS_PROTO_VERSION = tuple(map(int, wsproto.__version__.split('.')))

HOST = '127.0.0.1'
Expand Down Expand Up @@ -428,6 +448,91 @@ async def handler(request):
assert header_value == b'My test header'




@fail_after(5)
async def test_open_websocket_internal_ki(nursery, monkeypatch, autojump_clock):
"""_reader_task._handle_ping_event triggers KeyboardInterrupt.
user code also raises exception.
Make sure that KI is delivered, and the user exception is in the __cause__ exceptiongroup
"""
async def ki_raising_ping_handler(*args, **kwargs) -> None:
print("raising ki")
raise KeyboardInterrupt
monkeypatch.setattr(WebSocketConnection, "_handle_ping_event", ki_raising_ping_handler)
async def handler(request):
server_ws = await request.accept()
await server_ws.ping(b"a")

server = await nursery.start(serve_websocket, handler, HOST, 0, None)
with pytest.raises(KeyboardInterrupt) as exc_info:
async with open_websocket(HOST, server.port, RESOURCE, use_ssl=False):
with trio.fail_after(1) as cs:
cs.shield = True
await trio.sleep(2)

e_cause = exc_info.value.__cause__
assert isinstance(e_cause, EXCEPTION_GROUP_TYPE)
assert any(isinstance(e, trio.TooSlowError) for e in e_cause.exceptions)

@fail_after(5)
async def test_open_websocket_internal_exc(nursery, monkeypatch, autojump_clock):
"""_reader_task._handle_ping_event triggers ValueError.
user code also raises exception.
internal exception is in __cause__ exceptiongroup and user exc is delivered
"""
my_value_error = ValueError()
async def raising_ping_event(*args, **kwargs) -> None:
raise my_value_error

monkeypatch.setattr(WebSocketConnection, "_handle_ping_event", raising_ping_event)
async def handler(request):
server_ws = await request.accept()
await server_ws.ping(b"a")

server = await nursery.start(serve_websocket, handler, HOST, 0, None)
with pytest.raises(trio.TooSlowError) as exc_info:
async with open_websocket(HOST, server.port, RESOURCE, use_ssl=False):
with trio.fail_after(1) as cs:
cs.shield = True
await trio.sleep(2)

e_cause = exc_info.value.__cause__
assert isinstance(e_cause, EXCEPTION_GROUP_TYPE)
assert my_value_error in e_cause.exceptions

@fail_after(5)
async def test_open_websocket_cancellations(nursery, monkeypatch, autojump_clock):
"""Both user code and _reader_task raise Cancellation.
Check that open_websocket reraises the one from user code for traceback reasons.

We monkeypatch WebSocketConnection._handle_ping_event to ensure it will actually
raise Cancelled upon being cancelled. For some reason it doesn't otherwise."""
jakkdl marked this conversation as resolved.
Show resolved Hide resolved

async def sleeping_ping_event(*args, **kwargs) -> None:
await trio.sleep_forever()

monkeypatch.setattr(WebSocketConnection, "_handle_ping_event", sleeping_ping_event)
async def handler(request):
server_ws = await request.accept()
await server_ws.ping(b"a")
user_cancelled = None

server = await nursery.start(serve_websocket, handler, HOST, 0, None)
with trio.move_on_after(2):
with pytest.raises(trio.Cancelled) as exc_info:
async with open_websocket(HOST, server.port, RESOURCE, use_ssl=False):
try:
await trio.sleep_forever()
except trio.Cancelled as e:
user_cancelled = e
raise
assert exc_info.value is user_cancelled

def _trio_default_loose() -> bool:
jakkdl marked this conversation as resolved.
Show resolved Hide resolved
assert re.match(r'^0\.\d\d\.', trio.__version__), "unexpected trio versioning scheme"
return int(trio.__version__[2:4]) < 25

@fail_after(1)
async def test_handshake_exception_before_accept() -> None:
''' In #107, a request handler that throws an exception before finishing the
Expand All @@ -436,14 +541,28 @@ async def test_handshake_exception_before_accept() -> None:
async def handler(request):
raise ValueError()

with pytest.raises(ValueError):
# pylint fails to resolve that BaseExceptionGroup will always be available
with pytest.raises((BaseExceptionGroup, ValueError)) as exc: # pylint: disable=possibly-used-before-assignment
belm0 marked this conversation as resolved.
Show resolved Hide resolved
async with trio.open_nursery() as nursery:
server = await nursery.start(serve_websocket, handler, HOST, 0,
None)
async with open_websocket(HOST, server.port, RESOURCE,
use_ssl=False):
pass

if _trio_default_loose():
assert isinstance(exc.value, ValueError)
else:
# there's 4 levels of nurseries opened, leading to 4 nested groups:
# 1. this test
# 2. WebSocketServer.run
# 3. trio.serve_listeners
# 4. WebSocketServer._handle_connection
assert RaisesGroup(
RaisesGroup(
RaisesGroup(
RaisesGroup(ValueError)))).matches(exc.value)


@fail_after(1)
async def test_reject_handshake(nursery):
Expand Down
125 changes: 116 additions & 9 deletions trio_websocket/_impl.py
Copy link
Member

@belm0 belm0 Jun 6, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi John-- I may be slow in reviewing.

Please make sure the PR description summarizes the changes (e.g. mentions the internal error, API policy about exception groups, etc.).

Would need test coverage for any changes, but ok to hold off until I've reviewed the basics (as I can't promise we'll take the direction of this PR).

I'm itching to add Black and type checking to the CI, but that should be in a separate PR.

Please see #177. On type checking, I'm ok running a loose mypy pass, but reluctant to convert the codebase to strict type annotations, since fighting the type system is often a burden on maintenance (especially with a project on life support).

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah thank you, of course I'd complained about lack of Black before 😅

Agree on loose mypy just to check if the annotations that exist are correct. And I don't have any plans on adding annotations everywhere, just doing it for my own sake when developing.

Will try and make PR summary verbose and descriptive 👍

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

WebSocketServer.run and WebSocketServer._handle_connection are the other two places that opens a nursery. I've opted not to change these, since I don't think user code should expect any special exceptions from it, and it seems less obscure that it might contain an internal nursery.

In principle I'd like to state that the API doesn't raise exception groups, and that would include the server API. For the user's handler, perhaps add UserRequestHandlerException?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think that for users that are embracing strict_exception_groups=True and are used to handling exceptiongroups everywhere we shouldn't purposely obscure the groups and make errors harder for them to handle (and Trio's stance is that this is the default and should be embraced). I haven't delved too too deeply into them to see what it would imply to try and avoid exceptiongroups, but I think it might necessitate a change in API where we might end up changing what exceptions are being raised - even for users sticking with strict_exception_groups=False.

Original file line number Diff line number Diff line change
Expand Up @@ -13,6 +13,7 @@
import urllib.parse
from typing import Iterable, List, Optional, Union

import outcome
import trio
import trio.abc
from wsproto import ConnectionType, WSConnection
Expand Down Expand Up @@ -44,6 +45,13 @@
logger = logging.getLogger('trio-websocket')


class TrioWebsocketInternalError(Exception):
"""Raised as a fallback when open_websocket is unable to unwind an exceptiongroup
into a single preferred exception. This should never happen, if it does then
underlying assumptions about the internal code are incorrect.
"""


def _ignore_cancel(exc):
return None if isinstance(exc, trio.Cancelled) else exc

Expand Down Expand Up @@ -125,10 +133,33 @@ async def open_websocket(
client-side timeout (:exc:`ConnectionTimeout`, :exc:`DisconnectionTimeout`),
or server rejection (:exc:`ConnectionRejected`) during handshakes.
'''
async with trio.open_nursery() as new_nursery:

# This context manager tries very very hard not to raise an exceptiongroup
# in order to be as transparent as possible for the end user.
# In the trivial case, this means that if user code inside the cm raises
# we make sure that it doesn't get wrapped.

# If opening the connection fails, then we will raise that exception. User
# code is never executed, so we will never have multiple exceptions.

# After opening the connection, we spawn _reader_task in the background and
# yield to user code. If only one of those raise a non-cancelled exception
# we will raise that non-cancelled exception.
# If we get multiple cancelled, we raise the user's cancelled.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Multiple Cancelled was an existing possible case, so do we need to try hard to make it a single exception? (Cancelled is typically caught by trio itself, and otherwise the user had to deal with MultiError Cancelled anyway.)

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The problem is that it's a very easy gotcha to write

try:
  ...
except Cancelled:
  ...

which might work 99% of the time, but then at some random point you get multiple instead of a single (or the other way around) Cancelled, and your exception handler is now broken. I agree that Cancelled is perhaps a special case due to trio handling it, but if it does surface to the user I'm not sure there's much to be gained from having them see multiple of them.

Copy link
Member

@belm0 belm0 Sep 9, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

MultiError with Cancelled can happen fairly easily, and we quickly learned never to write except Cancelled in our application.

By this trio-websocket change, we're masking the user from the effects of a trio anti-pattern, which is concerning. For example, the user may get away with except Cancelled when the trio-websocket API is involved, but then be doubly puzzled when it doesn't work with another API.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hrm, I think this would be a very bad design choice. With this PR we're trying to make the internal nursery an implementation detail, as per https://trio.readthedocs.io/en/stable/reference-core.html#designing-for-multiple-errors
Before strict_exception_groups=True was the default it was expected that a trio developer would be able to handle the occasional MultiError, but since strict=True trio is trying very hard to make it fully consistent - either you always get an ExceptionGroup, or you never get one. And all other library APIs are encouraged to follow in those footsteps.

In the future the users shouldn't need to worry about this anti-pattern at all, so I do not think we should enshrine it in this API.

# If both raise exceptions, we raise the user code's exception with the entire
# exception group as the __cause__.
# If we somehow get multiple exceptions, but no user exception, then we raise
# TrioWebsocketInternalError.

# If closing the connection fails, then that will be raised as the top
# exception in the last `finally`. If we encountered exceptions in user code
# or in reader task then they will be set as the `__cause__`.


async def open_connection(nursery: trio.Nursery) -> WebSocketConnection:
belm0 marked this conversation as resolved.
Show resolved Hide resolved
try:
with trio.fail_after(connect_timeout):
connection = await connect_websocket(new_nursery, host, port,
return await connect_websocket(nursery, host, port,
resource, use_ssl=use_ssl, subprotocols=subprotocols,
extra_headers=extra_headers,
message_queue_size=message_queue_size,
Expand All @@ -137,14 +168,90 @@ async def open_websocket(
raise ConnectionTimeout from None
except OSError as e:
raise HandshakeError from e

async def close_connection(connection: WebSocketConnection) -> None:
try:
yield connection
finally:
try:
with trio.fail_after(disconnect_timeout):
await connection.aclose()
except trio.TooSlowError:
raise DisconnectionTimeout from None
with trio.fail_after(disconnect_timeout):
await connection.aclose()
except trio.TooSlowError:
raise DisconnectionTimeout from None

if _TRIO_MULTI_ERROR:
exception_group_type = trio.MultiError # type: ignore[attr-defined] # pylint: disable=no-member
else:
exception_group_type = BaseExceptionGroup
belm0 marked this conversation as resolved.
Show resolved Hide resolved

connection: WebSocketConnection|None=None
result2: outcome.Maybe[None] | None = None
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I forgot if we discussed already, but I think Optional[Foo] is more friendly / readable than Foo | None.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think |None is the standard way of doing it nowadays, and pyupgrade/ruff will warn on doing Optional[...]: https://docs.astral.sh/ruff/rules/non-pep604-annotation/

I also think it's nice for newbies not to have another keyword to know, and highly personally I prefer not having to do another import for it.

jakkdl marked this conversation as resolved.
Show resolved Hide resolved
user_error = None

try:
async with trio.open_nursery() as new_nursery:
result = await outcome.acapture(open_connection, new_nursery)

if isinstance(result, outcome.Value):
connection = result.unwrap()
try:
yield connection
except BaseException as e:
user_error = e
raise
finally:
result2 = await outcome.acapture(close_connection, connection)
# This exception handler should only be entered if either:
# 1. The _reader_task started in connect_websocket raises
# 2. User code raises an exception
# I.e. open/close_connection are not included
except exception_group_type as e:
# user_error, or exception bubbling up from _reader_task
if len(e.exceptions) == 1:
raise e.exceptions[0]

# contains at most 1 non-cancelled exceptions
exception_to_raise: BaseException|None = None
for sub_exc in e.exceptions:
if not isinstance(sub_exc, trio.Cancelled):
if exception_to_raise is not None:
# multiple non-cancelled
break
exception_to_raise = sub_exc
else:
if exception_to_raise is None:
# all exceptions are cancelled
# prefer raising the one from the user, for traceback reasons
if user_error is not None:
# no reason to raise from e, just to include a bunch of extra
# cancelleds.
raise user_error # pylint: disable=raise-missing-from
# multiple internal Cancelled is not possible afaik
raise e.exceptions[0] # pragma: no cover # pylint: disable=raise-missing-from
raise exception_to_raise

# if we have any KeyboardInterrupt in the group, make sure to raise it.
for sub_exc in e.exceptions:
if isinstance(sub_exc, KeyboardInterrupt):
raise sub_exc from e

# Both user code and internal code raised non-cancelled exceptions.
# We "hide" the internal exception(s) in the __cause__ and surface
# the user_error.
if user_error is not None:
raise user_error from e

raise TrioWebsocketInternalError(
"Multiple internal exceptions should not be possible. "
jakkdl marked this conversation as resolved.
Show resolved Hide resolved
"Please report this as a bug to "
"https://github.com/python-trio/trio-websocket"
) from e # pragma: no cover

finally:
if result2 is not None:
result2.unwrap()


# error setting up, unwrap that exception
if connection is None:
result.unwrap()


async def connect_websocket(nursery, host, port, resource, *, use_ssl,
Expand Down
Loading