Bug

The feishu adapter monkey-patches websockets.connect globally:

websockets.connect = _connect_with_overrides

However, _connect_with_overrides was declared as async def, which returns a coroutine object instead of a context manager. Since Python modules are singletons, this replaces the global websockets.connect (a normal function returning a context manager) with a coroutine function.

Impact

Any other platform that imports websockets and uses async with websockets.connect(uri) will crash with:

TypeError: "coroutine" object does not support the asynchronous context manager protocol

Confirmed broken: dingtalk (dingtalk_stream uses async with websockets.connect(uri)).

Potentially affected: any future gateway platform or third-party library that shares the same websockets module instance.

Root Cause

# Before (broken) — returns coroutine, not context manager
async def _connect_with_overrides(*args, **kwargs):
    ...
    return await original_connect(*args, **kwargs)

The await unwraps the context manager into a coroutine, breaking the async with protocol for all consumers.

Fix

# After (fixed) — returns context manager, same as original connect()
def _connect_with_overrides(*args, **kwargs):
    ...
    return original_connect(*args, **kwargs)

• async def → def: no longer a coroutine function
• return await original_connect(...) → return original_connect(...): returns the context manager object directly, preserving the original websockets.connect() interface
• Override logic (ping_interval / ping_timeout injection) is unchanged

Testing

Verified compatible with websockets 13.x, 15.x, and 16.x. All three gateway platforms (feishu, dingtalk, weixin) connect normally after the fix.