Github user DmytroShkvyra commented on the issue:
https://github.com/apache/zeppelin/pull/2002
@1ambda I repeat again (very slowly):
1. We cant install npm with frontend-maven-plugin locally. It throws a lot
of errors like this (zeppelin.log) this is attempt install npm with
frontend-maven-plugin in runtime. Errors with pom.xml are simmilar:
```
WARN [2017-02-09 18:20:34,011] ({main} Helium.java[loadConf]:119) -
/vagrant/zeppelin/conf/helium.json does not exists
ERROR [2017-02-09 18:20:35,296] ({main} Helium.java[getAllPackageInfo]:184)
- Directory
'/vagrant/zeppelin/local-repo/helium-registry-cache/https:/s3.amazonaws.com/helium-package'
could not be created
java.io.IOException: Directory
'/vagrant/zeppelin/local-repo/helium-registry-cache/https:/s3.amazonaws.com/helium-package'
could not be created
at
org.apache.commons.io.FileUtils.openOutputStream(FileUtils.java:363)
at
org.apache.commons.io.FileUtils.writeStringToFile(FileUtils.java:1928)
at
org.apache.commons.io.FileUtils.writeStringToFile(FileUtils.java:1962)
at
org.apache.zeppelin.helium.HeliumOnlineRegistry.writeToCache(HeliumOnlineRegistry.java:130)
at
org.apache.zeppelin.helium.HeliumOnlineRegistry.getAll(HeliumOnlineRegistry.java:101)
at
org.apache.zeppelin.helium.Helium.getAllPackageInfo(Helium.java:173)
at
org.apache.zeppelin.helium.Helium.getBundlePackagesToBundle(Helium.java:307)
at
org.apache.zeppelin.server.ZeppelinServer.<init>(ZeppelinServer.java:136)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
Method)
at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
at
org.apache.cxf.jaxrs.servlet.CXFNonSpringJaxrsServlet.createSingletonInstance(CXFNonSpringJaxrsServlet.java:382)
at
org.apache.cxf.jaxrs.servlet.CXFNonSpringJaxrsServlet.createApplicationInstance(CXFNonSpringJaxrsServlet.java:454)
at
org.apache.cxf.jaxrs.servlet.CXFNonSpringJaxrsServlet.createServerFromApplication(CXFNonSpringJaxrsServlet.java:432)
at
org.apache.cxf.jaxrs.servlet.CXFNonSpringJaxrsServlet.init(CXFNonSpringJaxrsServlet.java:93)
at
org.eclipse.jetty.servlet.ServletHolder.initServlet(ServletHolder.java:616)
at
org.eclipse.jetty.servlet.ServletHolder.initialize(ServletHolder.java:396)
at
org.eclipse.jetty.servlet.ServletHandler.initialize(ServletHandler.java:871)
at
org.eclipse.jetty.servlet.ServletContextHandler.startContext(ServletContextHandler.java:298)
at
org.eclipse.jetty.webapp.WebAppContext.startWebapp(WebAppContext.java:1349)
at
org.eclipse.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1342)
at
org.eclipse.jetty.server.handler.ContextHandler.doStart(ContextHandler.java:741)
at
org.eclipse.jetty.webapp.WebAppContext.doStart(WebAppContext.java:505)
at
org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
at
org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:132)
at
org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:114)
at
org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:61)
at
org.eclipse.jetty.server.handler.ContextHandlerCollection.doStart(ContextHandlerCollection.java:163)
at
org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
at
org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:132)
at org.eclipse.jetty.server.Server.start(Server.java:387)
at
org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:114)
at
org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:61)
at org.eclipse.jetty.server.Server.doStart(Server.java:354)
at
org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
at
org.apache.zeppelin.server.ZeppelinServer.main(ZeppelinServer.java:185)
ERROR [2017-02-09 18:20:53,185] ({main} ZeppelinServer.java[<init>]:138) -
Running 'npm run bundle --registry=http://registry.npmjs.org/' in
/vagrant/zeppelin/local-repo/helium-bundle
> zeppelin-helium-bundle@ bundle /vagrant/zeppelin/local-repo/helium-bundle
> node/node node_modules/webpack/bin/webpack.js --display-error-details
--json
module.js:471
throw err;
^
Error: Cannot find module
'/vagrant/zeppelin/local-repo/helium-bundle/node_modules/webpack/bin/webpack.js'
at Function.Module._resolveFilename (module.js:469:15)
at Function.Module._load (module.js:417:25)
at Module.runMain (module.js:604:10)
at run (bootstrap_node.js:394:7)
at startup (bootstrap_node.js:149:9)
at bootstrap_node.js:509:3
npm ERR! Linux 3.10.0-514.2.2.el7.x86_64
npm ERR! argv "/vagrant/zeppelin/local-repo/helium-bundle/node/node"
"/vagrant/zeppelin/local-repo/helium-bundle/node/node_modules/npm/bin/npm-cli.js"
"run" "bundle" "--registry=http://registry.npmjs.org/";
npm ERR! node v6.9.1
npm ERR! npm v3.10.8
npm ERR! code ELIFECYCLE
npm ERR! zeppelin-helium-bundle@ bundle: `node/node
node_modules/webpack/bin/webpack.js --display-error-details --json`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the zeppelin-helium-bundle@ bundle script 'node/node
node_modules/webpack/bin/webpack.js --display-error-details --json'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the
zeppelin-helium-bundle package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! node/node node_modules/webpack/bin/webpack.js
--display-error-details --json
npm ERR! You can get information on how to open an issue for this project
with:
npm ERR! npm bugs zeppelin-helium-bundle
npm ERR! Or if that isn't available, you can get their info via:
npm ERR! npm owner ls zeppelin-helium-bundle
npm ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request:
npm ERR! /vagrant/zeppelin/local-repo/helium-bundle/npm-debug.log
java.io.IOException: Running 'npm run bundle
--registry=http://registry.npmjs.org/' in
/vagrant/zeppelin/local-repo/helium-bundle
> zeppelin-helium-bundle@ bundle /vagrant/zeppelin/local-repo/helium-bundle
> node/node node_modules/webpack/bin/webpack.js --display-error-details
--json
module.js:471
throw err;
^
Error: Cannot find module
'/vagrant/zeppelin/local-repo/helium-bundle/node_modules/webpack/bin/webpack.js'
at Function.Module._resolveFilename (module.js:469:15)
at Function.Module._load (module.js:417:25)
at Module.runMain (module.js:604:10)
at run (bootstrap_node.js:394:7)
at startup (bootstrap_node.js:149:9)
at bootstrap_node.js:509:3
npm ERR! Linux 3.10.0-514.2.2.el7.x86_64
npm ERR! argv "/vagrant/zeppelin/local-repo/helium-bundle/node/node"
"/vagrant/zeppelin/local-repo/helium-bundle/node/node_modules/npm/bin/npm-cli.js"
"run" "bundle" "--registry=http://registry.npmjs.org/";
npm ERR! node v6.9.1
npm ERR! npm v3.10.8
npm ERR! code ELIFECYCLE
npm ERR! zeppelin-helium-bundle@ bundle: `node/node
node_modules/webpack/bin/webpack.js --display-error-details --json`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the zeppelin-helium-bundle@ bundle script 'node/node
node_modules/webpack/bin/webpack.js --display-error-details --json'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the
zeppelin-helium-bundle package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! node/node node_modules/webpack/bin/webpack.js
--display-error-details --json
npm ERR! You can get information on how to open an issue for this project
with:
npm ERR! npm bugs zeppelin-helium-bundle
npm ERR! Or if that isn't available, you can get their info via:
npm ERR! npm owner ls zeppelin-helium-bundle
npm ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request:
npm ERR! /vagrant/zeppelin/local-repo/helium-bundle/npm-debug.log
at
org.apache.zeppelin.helium.HeliumBundleFactory.buildBundle(HeliumBundleFactory.java:210)
at
org.apache.zeppelin.helium.HeliumBundleFactory.buildBundle(HeliumBundleFactory.java:105)
at
org.apache.zeppelin.server.ZeppelinServer.<init>(ZeppelinServer.java:136)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
Method)
at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
at
org.apache.cxf.jaxrs.servlet.CXFNonSpringJaxrsServlet.createSingletonInstance(CXFNonSpringJaxrsServlet.java:382)
at
org.apache.cxf.jaxrs.servlet.CXFNonSpringJaxrsServlet.createApplicationInstance(CXFNonSpringJaxrsServlet.java:454)
at
org.apache.cxf.jaxrs.servlet.CXFNonSpringJaxrsServlet.createServerFromApplication(CXFNonSpringJaxrsServlet.java:432)
at
org.apache.cxf.jaxrs.servlet.CXFNonSpringJaxrsServlet.init(CXFNonSpringJaxrsServlet.java:93)
at
org.eclipse.jetty.servlet.ServletHolder.initServlet(ServletHolder.java:616)
at
org.eclipse.jetty.servlet.ServletHolder.initialize(ServletHolder.java:396)
at
org.eclipse.jetty.servlet.ServletHandler.initialize(ServletHandler.java:871)
at
org.eclipse.jetty.servlet.ServletContextHandler.startContext(ServletContextHandler.java:298)
at
org.eclipse.jetty.webapp.WebAppContext.startWebapp(WebAppContext.java:1349)
at
org.eclipse.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1342)
at
org.eclipse.jetty.server.handler.ContextHandler.doStart(ContextHandler.java:741)
at
org.eclipse.jetty.webapp.WebAppContext.doStart(WebAppContext.java:505)
at
org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
at
org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:132)
at
org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:114)
at
org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:61)
at
org.eclipse.jetty.server.handler.ContextHandlerCollection.doStart(ContextHandlerCollection.java:163)
at
org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
at
org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:132)
at org.eclipse.jetty.server.Server.start(Server.java:387)
at
org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:114)
at
org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:61)
at org.eclipse.jetty.server.Server.doStart(Server.java:354)
at
org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
at
org.apache.zeppelin.server.ZeppelinServer.main(ZeppelinServer.java:185)
INFO [2017-02-09 18:20:55,830] ({main} InterpreterFactory.java[init]:247)
- InterpreterSettingRef name ignite
```
I have written about causes this behaviour - (limit of amount symlinks in
Linux and recursive style of package installation with npm and limit of stack
size for JS engines in different OSes).
See https://github.com/npm/npm/issues/9953
> you didn't try to understand my comments at all. I repeatedly said script
tags is not the problem.
I didn't say that these scripts "are problem". I just say that:
this:
```
"postinstall": "bower install --silent",
```
and this:
```
"pretest": "npm install karma-phantomjs-launcher",
```
Why?
Because when frontend-maven-plugin execute something like this:
```
<execution>
<id>yarn add bower</id>
<goals>
<goal>yarn</goal>
</goals>
<configuration>
<arguments>add bower --no-lockfile
--no-bin-links</arguments>
</configuration>
</execution>
```
or like this:
```
<execution>
<id>npm npm install</id>
<goals>
<goal>npm</goal>
</goals>
<configuration>
<arguments>install</arguments>
</configuration>
</execution>
```
it triggered **postinstall** and naturally it fails
Similar situation with
```
mvn test
```
It triggered **pretest** with same result.
Why we should use maven for build????
Because we can build all sub-modules by one command instead of run build
and test each sub module.
**CONCLUSION**: We should avoid use tags like "postinstall" and "pretest"
Do you agree?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
