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
I don't have a reproducible repo, so I'm creating a discussion instead of a bug, for now. Please let me know if I should scale up this to a bug
We have Verdaccio installed with the latest version, and we have some pipeline jobs that run automated tests that start by installing all needed dependencies. Those pipeline jobs run in parallel, since they are composed by tests that do not conflict with each other. When running the parallel pipeline jobs, verdaccio crashes. This causes our jobs to fail since dependencies can not be installed by NPM. This is my environment settings:
verdaccio version: 5.26.3
node version [12.x.x, 14.x.x]: 18.15.0
package manager: npm@9.5.0
os: linux
platform: docker
If I run the jobs one by one, instead of parallel, they will work. Verdaccio will not crash. We have gathered some logs that may help understand this issue. I've replaced some sensitive data by <redacted>
set 27 14:54:09 verdaccio docker-compose[2170431]: verdaccio | info <-- <redacted> requested 'GET /@types%2fyargs'
set 27 14:54:09 verdaccio docker-compose[2170431]: verdaccio | info --- auth/allow_action: access granted to: <redacted>
set 27 14:54:09 verdaccio docker-compose[2170431]: verdaccio | info --- allowed access for @types/yargs
set 27 14:54:09 verdaccio docker-compose[2170431]: verdaccio | http <-- 200, user: <redacted>(<redacted> via <redacted>), req: 'GET /@types%2fyargs', bytes: 0/0
set 27 14:54:32 verdaccio docker-compose[2170431]: verdaccio |
set 27 14:54:32 verdaccio docker-compose[2170431]: verdaccio | <--- Last few GCs --->
set 27 14:54:32 verdaccio docker-compose[2170431]: verdaccio |
set 27 14:54:32 verdaccio docker-compose[2170431]: verdaccio | [8:0x7f84efeea340] 485806 ms: Scavenge (reduce) 2041.0 (2080.0) -> 2041.0 (2080.8) MB, 4.7 / 0.0 ms (average mu = 0.185,>
set 27 14:54:32 verdaccio docker-compose[2170431]: verdaccio | [8:0x7f84efeea340] 485816 ms: Scavenge (reduce) 2042.1 (2080.8) -> 2042.1 (2082.0) MB, 5.8 / 0.0 ms (average mu = 0.185,>
set 27 14:54:32 verdaccio docker-compose[2170431]: verdaccio | [8:0x7f84efeea340] 486116 ms: Scavenge (reduce) 2043.1 (2082.0) -> 2043.1 (2083.3) MB, 15.9 / 0.0 ms (average mu = 0.185>
set 27 14:54:32 verdaccio docker-compose[2170431]: verdaccio |
set 27 14:54:32 verdaccio docker-compose[2170431]: verdaccio |
set 27 14:54:32 verdaccio docker-compose[2170431]: verdaccio | <--- JS stacktrace --->
set 27 14:54:32 verdaccio docker-compose[2170431]: verdaccio |
set 27 14:54:32 verdaccio docker-compose[2170431]: verdaccio | FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory
set 27 14:54:33 verdaccio docker-compose[2170431]: verdaccio exited with code 134
set 27 14:54:34 verdaccio docker-compose[2170431]: Stopping verdaccio ...
set 27 14:54:34 verdaccio docker-compose[2170431]: Stopping verdaccio ... done
set 27 14:54:34 verdaccio docker-compose[2170431]: Aborting on container exit...
set 27 14:54:35 verdaccio docker-compose[2171727]: Removing verdaccio ...
set 27 14:54:35 verdaccio docker-compose[2171727]: Removing verdaccio ... done
set 27 14:54:35 verdaccio docker-compose[2171727]: Removing network verdaccio_node-network
set 27 14:54:35 verdaccio systemd[1]: verdaccio.service: Deactivated successfully.
set 27 14:54:35 verdaccio systemd[1]: verdaccio.service: Consumed 23.725s CPU time.
set 27 14:54:37 verdaccio systemd[1]: verdaccio.service: Scheduled restart job, restart counter is at 4.
set 27 14:54:37 verdaccio systemd[1]: Stopped verdaccio.
set 27 14:54:37 verdaccio systemd[1]: verdaccio.service: Consumed 23.725s CPU time.
set 27 14:54:37 verdaccio systemd[1]: Starting verdaccio...
set 27 14:54:38 verdaccio docker-compose[2171789]: Removing network verdaccio_node-network
How can I solve this issue? Is this a verdaccio bug, or is it a misconfiguration on our side? I found #3765, but I don't think increasing Docker memory will help us, because we currently have it unlimited
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I don't have a reproducible repo, so I'm creating a discussion instead of a bug, for now. Please let me know if I should scale up this to a bug
We have Verdaccio installed with the latest version, and we have some pipeline jobs that run automated tests that start by installing all needed dependencies. Those pipeline jobs run in parallel, since they are composed by tests that do not conflict with each other. When running the parallel pipeline jobs, verdaccio crashes. This causes our jobs to fail since dependencies can not be installed by NPM. This is my environment settings:
If I run the jobs one by one, instead of parallel, they will work. Verdaccio will not crash. We have gathered some logs that may help understand this issue. I've replaced some sensitive data by <redacted>
How can I solve this issue? Is this a verdaccio bug, or is it a misconfiguration on our side? I found #3765, but I don't think increasing Docker memory will help us, because we currently have it unlimited
Beta Was this translation helpful? Give feedback.
All reactions