Skip to content

Introduce socketTimeout option #2965

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
May 20, 2025
Merged

Conversation

nkaradzhov
Copy link
Collaborator

@nkaradzhov nkaradzhov commented May 19, 2025

Description

Describe your pull request here


Checklist

  • Does npm test pass with this change (including linting)?
  • Is the new or changed code fully tested?
  • Is a documentation update included (if this change modifies existing APIs, or introduces new ones)?

@nkaradzhov nkaradzhov changed the title --wip--, needs validation, tests Introduce socketTimeout option May 19, 2025
@nkaradzhov nkaradzhov marked this pull request as draft May 19, 2025 12:42
@nkaradzhov nkaradzhov marked this pull request as ready for review May 19, 2025 14:27
The maximum duration (in milliseconds) that the socket can remain idle (i.e., with no data sent or received) before being automatically closed. Default reconnectionStrategy will ignore the new SocketTimeoutError, but users are allowed to have custom strategies wich handle those errors in different ways
@nkaradzhov nkaradzhov merged commit f3d1d33 into redis:master May 20, 2025
11 checks passed
@nkaradzhov nkaradzhov deleted the socket-timeout branch May 20, 2025 11:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants