Fix #387 Panic if Redis client returns use of closed network connection

[tdeverdiere]

Fixes #387

Proposed Changes

• Panic when the redis client receive use of closed network connection

[knative-prow]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: tdeverdiere
Once this PR has been reviewed and has the lgtm label, please assign skonto for approval. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[Cali0707]

Is there a more graceful way to handle this error? From the original issue, it seems like the proposed solution is:

Eventing-redis should reopen a socket when the error is "use of closed network connection".

I imagine that with this panicking, it will eventually be restarted and that would reopen the socket. But, I feel like we could handle this more gracefully. WDYT?

[github-actions]

This Pull Request is stale because it has been open for 90 days with
no activity. It will automatically close after 30 more days of
inactivity. Reopen with /reopen. Mark as fresh by adding the
comment /remove-lifecycle stale.