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

Fix incorrect numbers reported by DnsResolutionObserver#resolutionCompleted #1261

Merged
merged 1 commit into from
Dec 10, 2020

Conversation

idelpivnitskiy
Copy link
Member

Motivation:

DnsResolutionObserver#resolutionCompleted returns incorrect numbers for
ResolutionResult when some addresses become unavailable.

Modifications:

  • Fix metrics bug in ServiceDiscovererUtils.calculateDifference;
  • Add tests to verify we correctly report numbers when DNS returns different
    resolution updates;
  • Use BlockingQueue instead of List in DnsServiceDiscovererObserverTest;

Result:

DnsResolutionObserver#resolutionCompleted correctly reports number of
available and unavailable records.

…mpleted`

Motivation:

`DnsResolutionObserver#resolutionCompleted` returns incorrect numbers for
`ResolutionResult` when some addresses become unavailable.

Modifications:

- Fix metrics bug in `ServiceDiscovererUtils.calculateDifference`;
- Add tests to verify we correctly report numbers when DNS returns different
resolution updates;

Result:

`DnsResolutionObserver#resolutionCompleted` correctly reports number of
available and unavailable records.
@idelpivnitskiy
Copy link
Member Author

Test failure #1265

@servicetalk-bot test this please

@idelpivnitskiy idelpivnitskiy merged commit c2e07f3 into apple:main Dec 10, 2020
@idelpivnitskiy idelpivnitskiy deleted the ResolutionResultBug branch December 10, 2020 17:36
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