Skip to content
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

docs: improve docs on connect_timeout vs options.retry_strategy and some testing help #1531

Merged
merged 3 commits into from
Mar 4, 2021

Conversation

marnikvde
Copy link

Description

It took me quite some time to figure out why the auto-reconnect stopped after 1 hour, even when trying all possible different retry_strategy options, which turned out to be undocumented connect_timeout parameter. The code comments mentions that this behaviour should be changed in v3.0, but apparently that has not been implemented yet, so my addition to the docs seems correct. Not sure if related to #1444.

I also added a bit more info to be able to run the tests, and fixed some whitespaces.

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)?

@marnikvde
Copy link
Author

Not sure what is wrong with the actions, I tried on my fork and the "Run ataylorme/[email protected]" works just fine there (I changed the "on pull request" to "push", but that's probably not the problem. Here it errors with "##[error]Resource not accessible by integration".

@gkorland gkorland merged commit 49c4131 into redis:master Mar 4, 2021
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.

3 participants