-
Notifications
You must be signed in to change notification settings - Fork 437
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
fix: remove retries for instance-lookup #802
base: master
Are you sure you want to change the base?
Conversation
removed option.retrries from instance-lookup.js, this option does not exist and it is never passed from connection.js.
@Suraiya-Hameed I'm wondering why we even had this option in the first place. 🤔 |
Same here. From issue #195, probably the were intending to remove retries but missed it! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is an old PR but I believe the fix is still valid.
Codecov Report
@@ Coverage Diff @@
## master #802 +/- ##
==========================================
- Coverage 80.77% 79.84% -0.93%
==========================================
Files 86 86
Lines 4384 4376 -8
Branches 793 791 -2
==========================================
- Hits 3541 3494 -47
- Misses 584 626 +42
+ Partials 259 256 -3
Continue to review full report at Codecov.
|
@arthurschreiber eslint test is failing because of previous commit messages not following commitlint convention. Not sure how to fix. But overall this PR has been updated 😄 |
@IanChokS I double checked this. This removes the I think maybe we should remove the retries option, but also exposing a way to abort the lookup? Then we could just keep on retrying until we hit the connection timeout. @IanChokS @MichaelSun90 what do you think? |
Removed option.retries from instance-lookup.js, this option does not exist and it is never passed from connection.js.
Also, fixes #672