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

Do not resolve IP on __init__ #9644

Merged
merged 1 commit into from
Jul 7, 2021

Conversation

hithwen
Copy link
Contributor

@hithwen hithwen commented Jul 7, 2021

If IP resolution fails on check __init__ it will never be reattempted. This PR makes IP resolution lazy so it happens on check run instead of __init__. Upon connection failure it now forces a reevaluation on next check run instead of straight away.

@hithwen hithwen requested a review from a team as a code owner July 7, 2021 10:12
@ghost ghost added the integration/tcp_check label Jul 7, 2021
@codecov
Copy link

codecov bot commented Jul 7, 2021

Codecov Report

Merging #9644 (87b4fcf) into master (30abc06) will increase coverage by 0.00%.
The diff coverage is 79.31%.

Flag Coverage Δ
tcp_check 87.95% <79.31%> (+1.41%) ⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

@hithwen hithwen merged commit 88c4156 into master Jul 7, 2021
@hithwen hithwen deleted the js/AGENT-6539-do-not-resolve-ip-on-init branch July 7, 2021 15:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants