-
Notifications
You must be signed in to change notification settings - Fork 43
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
BUG: does not handle own CancelledError on client.close() #7
Comments
Same issue here. Is this project still maintained? |
|
Made my own! |
brberry
added a commit
to brberry/aiocometd-ng
that referenced
this issue
Apr 15, 2024
brberry
added a commit
to brberry/aiocometd-ng
that referenced
this issue
Apr 15, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
great project, thank you
in v 0.4.5: BUG: does not handle own CancelledError on client.close():
in
aiocometd/transports/base.py
:https://github.com/robertmrk/aiocometd/blob/0.4.5/aiocometd/transports/base.py#L541
in
aiocometd/transports/websocket.py
:https://github.com/robertmrk/aiocometd/blob/0.4.5/aiocometd/transports/websocket.py#L261
in both cases these are internal tasks, which are both created and canceled by
aiocometd
,and they both propagate own
aiocometd
initiatedCancelledError
to the event loopexception handler
The text was updated successfully, but these errors were encountered: