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

GEODE-3539: Add missing test coverage for 'describe connection' command. #797

Merged

Conversation

PurelyApplied
Copy link
Member

@PurelyApplied PurelyApplied commented Sep 19, 2017

Precheckin running.

Thank you for submitting a contribution to Apache Geode.

In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:

For all changes:

  • Is there a JIRA ticket associated with this PR? Is it referenced in the commit message?

  • Has your PR been rebased against the latest commit within the target branch (typically develop)?

  • Is your initial contribution a single, squashed commit?

  • Does gradlew build run cleanly?

  • Have you written or updated unit tests to verify your changes?

  • If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?

Note:

Please ensure that once the PR is submitted, you check travis-ci for build issues and
submit an update to your PR as soon as possible. If you need help, please send an
email to dev@geode.apache.org.

@PurelyApplied
Copy link
Member Author

New test failed in precheckin failed due to IPv4 vs IPv6 discrepancy. Correction pending.

@PurelyApplied PurelyApplied force-pushed the geode-3539-describe.connection branch 2 times, most recently from 98e3bbf to 521a93c Compare November 1, 2017 17:16
Enumeration<NetworkInterface> networkInterfaces = NetworkInterface.getNetworkInterfaces();
NetworkInterface myInterface = networkInterfaces.nextElement();
Enumeration<InetAddress> myAddresses = myInterface.getInetAddresses();
return StreamSupport
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Since this Enumeration will be reliably bounded (finite), I think we can turn it into a stream more concisely:

Collections.list(myAddresses).stream()
.map(InetAddress::getHostAddress)
.map(address -> formatAddressAndPort(address, locator.getJmxPort())).toArray(String[]::new);

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That's much less cudgel-y! Thanks.

}
}
failWithMessage("No accepted value found.");
return null;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think you can still return this rather than returning null. (For instance, someone might be using a JUnit rule that gathers up exceptions and re-throws them at the end of a sequence of operations. We wouldn't want to give them a NPE here in that case.)

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I hadn't even considered that scenario. Done and done.

@jaredjstewart
Copy link
Contributor

Looks good overall!

@PurelyApplied PurelyApplied merged commit a1b9725 into apache:develop Nov 6, 2017
@PurelyApplied PurelyApplied deleted the geode-3539-describe.connection branch November 14, 2017 18:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
3 participants