Got ERR_SOCKET_TIMEOUT when I build plugins locally due pnpm-lock.yaml has https://registry.yarnpkg.com

[initdc]

Describe the bug

A clear and concise description of what the bug is.

To Reproduce

Steps to reproduce the behavior:

1. China local
2. npm config set registry https://registry.npmmirror.com
3. Go to 'apache-answer-1.4.1-incubating-bin-linux-amd64' unzip folder

./answer build \
    --with github.com/apache/incubator-answer-plugins/connector-basic \
    --with github.com/apache/incubator-answer-plugins/connector-github \
    --with github.com/apache/incubator-answer-plugins/connector-google \
    --with github.com/apache/incubator-answer-plugins/storage-s3 \
    --with github.com/apache/incubator-answer-plugins/embed-basic \
    --with github.com/apache/incubator-answer-plugins/editor-chart

Resolve

Maybe you should delete pnpm-lock.yaml and re generate it

[shuashuai]

This kind of problem is related to the network and mirroring. You can first copy the resource link starting with https://registry.yarnpkg.com to the browser to see if it can be opened normally. If not, you can determine that it is a network problem.

Then you can manually find the link containing https://registry.yarnpkg.com from the pnpm-lock.yaml file, and then manually replace it with https://registry.npmmirror.com to completing the build, of course I will also macro update the pnpm version and lock file in the next version.

[afischer-opentext-com]

I am trying to add some plugins (by creating a new answer binary) and run into the issue as well. This is an isolated environment with mirror access only. I am following https://answer.apache.org/docs/plugins#docker-build here. Can someone confirm please that modifying the pnpm-lock.yaml is not possible that way as it is not pre-existing before running ./answer build? Would there be another workaround?