Fix NPE with no active network interfaces and HostnameFetcher Java 17+ reflection fallback#518
Merged
Merged
Conversation
Copilot
AI
changed the title
Fix reported exception bugs: Gradle 9 compat, NPE with no network interfaces, HostnameFetcher Java 17
Fix NPE with no active network interfaces, HostnameFetcher Java 17+ reflection, and Gradle 9 compat
Jun 8, 2026
Copilot created this pull request from a session on behalf of
angryziber
June 8, 2026 06:59
View session
…ameFetcher reflection fallback
- Fix build.gradle to use java {} block for source/target compatibility (issue #516)
- Fix NPE in AbstractFeederGUI.asyncFillLocalHostInfo() when no active network
interfaces exist: localInterface can be null, causing NPE in the UnknownHostException
catch block and in the asyncExec callback (issue #340)
- Fix HostnameFetcher.resolveWithRegularDNS() to explicitly guard the reflection
path when getHostByAddr is null (Java 17+ module system incompatibility)
Copilot
AI
force-pushed
the
copilot/find-reported-issues
branch
from
June 8, 2026 07:51
c82c4db to
daaedd9
Compare
Copilot
AI
changed the title
Fix NPE with no active network interfaces, HostnameFetcher Java 17+ reflection, and Gradle 9 compat
Fix NPE with no active network interfaces and HostnameFetcher Java 17+ reflection fallback
Jun 8, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Two independent crash bugs, both caused by implicit assumptions that break in edge-case environments.
NPE when all interfaces are DOWN (#340)
InetAddressUtils.getLocalInterface()returnsnullwhen no non-loopback interface with a hardware address is up.AbstractFeederGUI.asyncFillLocalHostInfo()dereferenced it unconditionally in both theUnknownHostExceptioncatch block and theasyncExeccallback.HostnameFetcher silent NPE on Java 17+
On Java 17+, the
HostnameFetcherstatic initializer fails withInaccessibleObjectException(module system blocksInetAddress.impl), leavinggetHostByAddr = null.resolveWithRegularDNS()relied on the subsequent NPE being swallowed by a broadcatch (Exception e)to fall through togetCanonicalHostName(). Replaced with an explicitif (getHostByAddr != null)guard so the fallback is unconditional and the exception handling only covers the intendedInvocationTargetException/UnknownHostExceptionpath.