You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 21, 2023. It is now read-only.
We migrated to aioredis 2.0 this week and we are seeing this error showing up once and again.
Unfortunately I have no clue how to reproduce it, it seems to happen randomly when setting a variable. It feels like the exception is showing up more and more often as the program runs. The code runs on multiple machines and we see the same issue on all of them
To Reproduce
I dont have a reliable way to reproduce this, but this is the function in which it happens:
async def rd_set(key, data, host="redis", port=6379):
try:
# Connect to redis & set key
rd = await aioredis.from_url(
f"redis://{host}:{port}", encoding="utf-8", decode_responses=True
)
async with rd.client() as conn:
await conn.set(key, data)
except ConnectionRefusedError:
send_warning()
logger.error(f"Unable to connect to redis, key '{key}' not updated!")
Expected behavior
We expect the function to not throw an exception and continue quietly
Logs/tracebacks
hub_1 | Traceback (most recent call last):
hub_1 | File "/code/metal_hub/handlers/redis.py", line 48, in handle_event
hub_1 | await rd_set("state", event.value)
hub_1 | File "/code/metal_hub/handlers/redis.py", line 83, in rd_set
hub_1 | await conn.set(key, data)
hub_1 | File "/usr/local/lib/python3.8/site-packages/aioredis/client.py", line 1064, in execute_command
hub_1 | return await self.parse_response(conn, command_name, **options)
hub_1 | File "/usr/local/lib/python3.8/site-packages/aioredis/client.py", line 1080, in parse_response
hub_1 | response = await connection.read_response()
hub_1 | RuntimeError: coroutine ignored GeneratorExit
Describe the bug
We migrated to aioredis 2.0 this week and we are seeing this error showing up once and again.
Unfortunately I have no clue how to reproduce it, it seems to happen randomly when setting a variable. It feels like the exception is showing up more and more often as the program runs. The code runs on multiple machines and we see the same issue on all of them
To Reproduce
I dont have a reliable way to reproduce this, but this is the function in which it happens:
Expected behavior
We expect the function to not throw an exception and continue quietly
Logs/tracebacks
Python Version
Python 3.8.12
aioredis Version
Additional context
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: