Normal timeouts in non-blocking reads result in continuous error messages

[fsedano]

Expected Behavior

On a stable environment, when using non-blocking reads in redis pubsub, I would not expect to see any errors from sidecar.

Actual Behavior

When using non-blocking reads in redis pubsub, when the context is cancelled upon timeout expiry, daprd is printing a message at Error level:

{"app_id":"test-utils","component":"pubsub (pubsub.redis/v1)","instance":"test-utils-okteto-6f86bf67db-gglfx","level":"error","msg":"redis streams: error reading from stream topo_mapper_response: read tcp 10.42.3.119:45460-\u003e10.42.4.182:6379: i/o timeout","scope":"dapr.contrib","time":"2025-11-07T01:19:07.794242894Z","type":"log","ver":"1.16.2"}
{"app_id":"test-utils","component":"pubsub (pubsub.redis/v1)","instance":"test-utils-okteto-6f86bf67db-gglfx","level":"error","msg":"redis streams: error reading from stream topo_mapper_response: read tcp 10.42.3.119:45478-\u003e10.42.4.182:6379: i/o timeout","scope":"dapr.contrib","time":"2025-11-07T01:19:08.794528802Z","type":"log","ver":"1.16.2"}

Steps to Reproduce the Problem

Configure a redis pubsub component with a timeout of 1s:

• name: readTimeout value: 1s

Errors will be printed every second in sidecar.

Release Note

RELEASE NOTE: FIX Bug in runtime.

[github-actions[bot]]

This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged (pinned, good first issue, help wanted or triaged/resolved) or other activity occurs. Thank you for your contributions.

[github-actions[bot]]

This issue has been automatically closed because it has not had activity in the last 37 days. If this issue is still valid, please ping a maintainer and ask them to label it as pinned, good first issue, help wanted or triaged/resolved. Thank you for your contributions.