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

[Bug] Hubble image build fails after introduce front-end download proxy #584

Open
1 task done
liuxiaocs7 opened this issue Mar 1, 2024 · 5 comments
Open
1 task done
Labels
bug Something isn't working ci Continuous integration hubble hugegraph-hubble

Comments

@liuxiaocs7
Copy link
Member

Bug Type (问题类型)

None

Before submit

  • I had searched in the issues and found no similar issues.

Environment (环境信息)

  • Server Version: v1.x.x
  • Toolchain Version: v1.x.x
  • Data Size: xx vertices, xx edges

Expected & Actual behavior (期望与实际表现)

https://github.com/hugegraph/actions/actions/runs/8103879676

Vertex/Edge example (问题点 / 边数据举例)

No response

Schema [VertexLabel, EdgeLabel, IndexLabel] (元数据结构)

No response

@liuxiaocs7 liuxiaocs7 added the bug Something isn't working label Mar 1, 2024
Copy link

dosubot bot commented Mar 1, 2024

It seems like you've got this under control, if you want help or have specific questions, let me know what I can do for you!

About Dosu

This response is meant to be useful and save you time. It is not meant to be a precise solution, but rather a starting point for your own research.

Help me be more useful! Please leave a 👍 if this is helpful and 👎 if it is irrelevant.

If you want to continue the conversation, start your reply with @dosu-bot.

@dosubot dosubot bot added ci Continuous integration hubble hugegraph-hubble labels Mar 1, 2024
@liuxiaocs7
Copy link
Member Author

liuxiaocs7 commented Mar 3, 2024

related: yarnpkg/yarn#4890

The highest voting comment:
image

@liuxiaocs7
Copy link
Member Author

liuxiaocs7 commented May 17, 2024

https://github.com/apache/incubator-hugegraph-toolchain/actions/runs/9116353718/job/25114755444?pr=604

[INFO] --- frontend-maven-plugin:1.14.2:yarn (yarn install) @ hubble-dist ---
[INFO] Running 'yarn install --network-timeout 600000' in /home/runner/work/incubator-hugegraph-toolchain/incubator-hugegraph-toolchain/hugegraph-hubble/hubble-dist/../hubble-fe
[INFO] yarn install v1.22.21
[INFO] [1/4] Resolving packages...
[INFO] [2/4] Fetching packages...
[INFO] info There appears to be trouble with your network connection. Retrying...
[INFO] info There appears to be trouble with your network connection. Retrying...
[INFO] info There appears to be trouble with your network connection. Retrying...
[INFO] info There appears to be trouble with your network connection. Retrying...
[INFO] info There appears to be trouble with your network connection. Retrying...
[INFO] error Error: getaddrinfo ENOTFOUND registry.nlark.com
[INFO]     at GetAddrInfoReqWrap.onlookup [as oncomplete] (node:dns:109:26)
[INFO] error Error: getaddrinfo ENOTFOUND registry.nlark.cominfo Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.
[INFO] info There appears to be trouble with your network connection. Retrying...
[INFO] info There appears to be trouble with your network connection. Retrying...
[INFO] info There appears to be trouble with your network connection. Retrying...
[INFO] info There appears to be trouble with your network connection. Retrying...

refer: https://stackoverflow.com/questions/39592908/error-getaddrinfo-enotfound-registry-npmjs-org-registry-npmjs-org443

@liuxiaocs7
Copy link
Member Author

@dosu-bot Please analyze the causes of the above problems and provide solutions

Copy link

dosubot bot commented May 17, 2024

The getaddrinfo ENOTFOUND registry.nlark.com error you're encountering during the yarn install process suggests a DNS resolution issue, where the domain registry.nlark.com cannot be found. This could be due to several reasons, including network connectivity issues, incorrect registry configuration, or DNS settings. Here's how to address the problem:

  1. Verify and Update DNS Settings: Ensure your DNS settings are correctly configured. Consider using a public DNS like Google's 8.8.8.8 or Cloudflare's 1.1.1.1.

  2. Check Yarn Registry Configuration: Use yarn config set registry https://registry.npmjs.org/ to set the registry to a known, reliable one. This step ensures Yarn attempts to fetch packages from the correct source.

  3. Clear Yarn Cache: Run yarn cache clean to clear any potentially corrupted cache that might be causing issues.

  4. Review and Update Dependencies: Check your package.json for any dependencies that might be pointing to registry.nlark.com and update them to use a more reliable registry.

  5. Check Network Connectivity: Ensure your internet connection is stable and that registry.nlark.com is not blocked by any firewall or network policy.

  6. Disable Proxy/VPN Temporarily: If you're using a proxy or VPN, disable it temporarily to check if it's causing the DNS resolution issue.

  7. Update Yarn: Ensure you're using the latest version of Yarn by running npm install -g yarn.

If these steps do not resolve the issue, it might be due to a temporary problem with the registry itself, in which case waiting for a resolution or contacting the registry's support might be necessary.

Details

Sources


About Dosu
This response is meant to be useful and save you time. It is not meant to be a precise solution, but rather a starting point for your own research.

Help me be more useful! Please leave a 👍 if this is helpful and 👎 if it is irrelevant.

To continue the conversation, mention @dosu.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working ci Continuous integration hubble hugegraph-hubble
Projects
None yet
Development

No branches or pull requests

1 participant