Closed jasonwbarnett closed 1 week ago
ping
's message
is typed to be bytes
https://github.com/aio-libs/aiohttp/blob/be31bed20210b6d7380aed8702a17994ea6a2d59/aiohttp/client_ws.py#L229
Change
await self.current_session.ping(f"sdk-ping-pong:{t}")
to
await self.current_session.ping(f"sdk-ping-pong:{t}".encode("utf-8"))
Looks like it was always typed that way on 3.10 as well https://github.com/aio-libs/aiohttp/blob/f5d5da43b05af7f62a40dff8a87e9c1a9bd479a2/aiohttp/client_ws.py#L217
Looks like its a bug in the slack_sdk
that was relying on the writer auto converting it internally which doesn't happen anymore in 3.11
Gotcha. Just seemed like a break in contract, but I guess what you're saying is that this caller was broken the whole time. I'll post a PR shortly to https://github.com/slackapi/python-slack-sdk
Thanks
I guess what you're saying is that this caller was broken the whole time.
Yup, It was a bit of luck that it worked before.
Closing this since the fix needs to happen in https://github.com/slackapi/python-slack-sdk/issues/1592
Describe the bug
After upgrading from 3.10.x to 3.11.x when starting a simple slack bolt app, an exception is raised.
To Reproduce
Create
socket_mode_async.py
from this source.pip install "aiohttp>=3.11.2"
export vars
Run app
Expected behavior
I would expect any changes from 3.10 to 3.11 to not break callers and for this to work just like it did in 3.10.x.
Logs/tracebacks
Python Version
aiohttp Version
multidict Version
propcache Version
yarl Version
OS
Ubuntu 22.04
Related component
Client
Additional context
No response
Code of Conduct