You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
I was getting "Response timeout while trying to fetch https://registry.npmjs.org/@vue%2fcli" as I tried to built the workspace, but as far as i saw there should be other trouble points and not only in the workspace container built.
Describe the solution you'd like
Add a workspace .env file timeout. But it could be something more global, I saw a few timeout variables, but nothing global.
Bellow the code I changed to add the timeout:
diff --git a/workspace/Dockerfile b/workspace/Dockerfile
index 6d059ba..9440904 100644
--- a/workspace/Dockerfile+++ b/workspace/Dockerfile@@ -678,6 +678,7 @@ RUN if [ ${INSTALL_NODE} = true ]; then \
&& nvm install ${NODE_VERSION} \
&& nvm use ${NODE_VERSION} \
&& nvm alias ${NODE_VERSION} \
+ && npm config set fetch-retry-maxtimeout 60000 -g \
&& if [ ${NPM_REGISTRY} ]; then \
npm config set registry ${NPM_REGISTRY} \
;fi \
To the final implementation I would create a variable WORKSPACE_NPM_TIMEOUT similar to the WORKSPACE_NPM_REGISTRY implementation in which it is applied only if the variable has some value, which would be numerical only.
Describe alternatives you've considered
Add something like GLOBAL_TIMEOUT instead WORKSPACE_NPM_TIMEOUT
Additional context
The original command I was executing to run into this problem was
docker-compose up -d nginx
I got into this problem when I was installing the latest tag version but my boss told-me to use v8.0 of laradock, when I restart the containers I was already with the timeout therefor I don't know if this would be an issue on v8.0
If anyone can tell me the team workflow I guess I can create a PR for this quite quickly.I'm new to the project. I have no idea how the community here behaves, I looked for something similar in the documentation and opened the issue for I didn't find anything, maybe some adjustment in the documentation is enough.
But if you decide to create the variable, I believe I can provide the procedure. I just don't know how to perform the procedure. I'd do a branch with the name of the variable and then open a PR for review. If so, I guess I could help!
Is your feature request related to a problem? Please describe.
I was getting "Response timeout while trying to fetch https://registry.npmjs.org/@vue%2fcli" as I tried to built the workspace, but as far as i saw there should be other trouble points and not only in the workspace container built.
Describe the solution you'd like
Add a workspace .env file timeout. But it could be something more global, I saw a few timeout variables, but nothing global.
Bellow the code I changed to add the timeout:
To the final implementation I would create a variable
WORKSPACE_NPM_TIMEOUT
similar to theWORKSPACE_NPM_REGISTRY
implementation in which it is applied only if the variable has some value, which would be numerical only.Describe alternatives you've considered
Add something like
GLOBAL_TIMEOUT
insteadWORKSPACE_NPM_TIMEOUT
Additional context
The original command I was executing to run into this problem was
I got into this problem when I was installing the latest tag version but my boss told-me to use v8.0 of laradock, when I restart the containers I was already with the timeout therefor I don't know if this would be an issue on v8.0
System environment
The text was updated successfully, but these errors were encountered: