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

On macOS Sierra, it takes several seconds to resolve the local hostname #736

Closed
big-guy opened this issue Oct 20, 2016 · 4 comments
Closed

Comments

@big-guy
Copy link
Member

big-guy commented Oct 20, 2016

Other Java tools are experiencing a problem with looking up the local hostname on macOS Sierra (10.12). Here's a longer description of the problem: https://thoeni.io/post/macos-sierra-java/

Expected Behavior

Local host look-up should be speedy, or if not, cached.

Current Behavior

I suspect this causing a problem here:
https://discuss.gradle.org/t/gradle-always-execute-creating-new-in-memory-cache-for-repo-maven-when-i-build-project-i-configurated-org-gralde-daemon-true-in-gradle-properties-the-command-line-properties-like-org-gradle-daemon-true-are-ignored/20080

Context

We have an uncached hostname look-up here:
https://github.com/gradle/gradle/blob/master/subprojects/resources-http/src/main/java/org/gradle/internal/resource/transport/http/ntlm/NTLMCredentials.java#L64

We have a cache in InetAddressFactory for this look-up that we could re-use. This has a large impact on builds with many repositories.

Steps to Reproduce (for bugs)

This happens always.

Your Environment

macOS Sierra

@twoseat
Copy link

twoseat commented Oct 20, 2016

Of possible relevance: https://thoeni.io/post/macos-sierra-java/

@oehme
Copy link
Contributor

oehme commented Jul 7, 2017

It seems to be an issue in the JDK actually, calling an inefficient native method: http://bugs.java.com/bugdatabase/view_bug.do?bug_id=8170910

I guess we could work around this by implementing our own logic in native-platform. We should also push for a solution to this issue.

@stale
Copy link

stale bot commented Jul 1, 2020

This issue has been automatically marked as stale because it has not had recent activity. Given the limited bandwidth of the team, it will be automatically closed if no further activity occurs. If you're interested in how we try to keep the backlog in a healthy state, please read our blog post on how we refine our backlog. If you feel this is something you could contribute, please have a look at our Contributor Guide. Thank you for your contribution.

@stale stale bot added the stale label Jul 1, 2020
@stale
Copy link

stale bot commented Jul 22, 2020

This issue has been automatically closed due to inactivity. If you can reproduce this on a recent version of Gradle or if you have a good use case for this feature, please feel free to reopen the issue with steps to reproduce, a quick explanation of your use case or a high-quality pull request.

@stale stale bot closed this as completed Jul 22, 2020
@wolfs wolfs closed this as not planned Won't fix, can't repro, duplicate, stale Sep 16, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants