Github user lwmonster commented on the issue:
https://github.com/apache/zeppelin/pull/2002
I installed nodejs and npm before package zeppelin, but another error
occurs, a timeout occurs; someone says that it is the yarn problem, and I use
the yarn-1.0.2 got a similar error as below,
Github user AtulKumVerma commented on the issue:
https://github.com/apache/zeppelin/pull/2002
./bin/spark-shell --jars
Github user AtulKumVerma commented on the issue:
https://github.com/apache/zeppelin/pull/2002
i am not able to get data from hbase using spark hbase connector,
any one did this so plz let me know all of its hbase,spark and other
configuation.
i got Error...
Github user lwmonster commented on the issue:
https://github.com/apache/zeppelin/pull/2002
Should I need to modify some files? @1ambda
---
Github user lwmonster commented on the issue:
https://github.com/apache/zeppelin/pull/2002
Now it is 2017-09-20, and I cloned the master branch, and it still have
error:
```
[INFO] [4/4] Building fresh packages...
[INFO] $ bower install --silent
[ERROR] [{
[ERROR]
Github user DmytroShkvyra commented on the issue:
https://github.com/apache/zeppelin/pull/2002
Incompatible with https://github.com/apache/zeppelin/pull/2016
---
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
Github user DmytroShkvyra commented on the issue:
https://github.com/apache/zeppelin/pull/2002
Installation of hidden dependencies was removed. (accordingly to reviewers
comments).
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub
Github user DmytroShkvyra commented on the issue:
https://github.com/apache/zeppelin/pull/2002
@1ambda
>Could you share the content of
/vagrant/zeppelin/local-repo/helium-bundle/npm-debug.log? when node/node
node_modules/webpack/bin/webpack.js --display-error-details --json
Github user DmytroShkvyra commented on the issue:
https://github.com/apache/zeppelin/pull/2002
Failed tests:
IgniteSqlInterpreterTest.testSql:95 expected: but was:
This test do not related with PR.
---
If your project is set up for it, you can reply to this email and have
Github user DmytroShkvyra commented on the issue:
https://github.com/apache/zeppelin/pull/2002
@1ambda
> I think we don't need to worry about max call stack size since it
occurs in unusual env like windows, linux on vm.
> Zeppelin is not the thing like JDK. There is no
Github user DmytroShkvyra commented on the issue:
https://github.com/apache/zeppelin/pull/2002
@1ambda BTW I have reverted my changes in README.md for build and test from
CL and add section about build and test with maven like this example:
```
mvn test -Dmaven.clean.skip=true
Github user 1ambda commented on the issue:
https://github.com/apache/zeppelin/pull/2002
@DmytroShkvyra
- I think we don't need to worry about **max call stack size** since it
occurs in unusual env like windows, *linux on vm*.
- Zeppelin is not the thing like JDK. There
Github user DmytroShkvyra commented on the issue:
https://github.com/apache/zeppelin/pull/2002
@1ambda No, I want make "normal|classical" maven project which do not need
preinstall everybody nodejs and their packages by hand. More over - yarn works
faster than npm
---
If your
Github user 1ambda commented on the issue:
https://github.com/apache/zeppelin/pull/2002
So, what you want to solve is **building zeppelin in vms which can't have
enough symlinks**? right?
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user DmytroShkvyra commented on the issue:
https://github.com/apache/zeppelin/pull/2002
@1ambda Yes, this different from build, but cause the same. Helium
installed npm with frondend-maven-plugin.
BTW. Many contributors cant use windows because this is proprietary and
Github user 1ambda commented on the issue:
https://github.com/apache/zeppelin/pull/2002
@DmytroShkvyra
I think the log you'v just posted is quite different. It's not for build.
---
If your project is set up for it, you can reply to this email and have your
reply appear on
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
Github user 1ambda commented on the issue:
https://github.com/apache/zeppelin/pull/2002
Regrading to **max call stack size** what @DmytroShkvyra mentioned in above
comment (for other people)
- https://github.com/npm/npm/issues/9953
-
Github user 1ambda commented on the issue:
https://github.com/apache/zeppelin/pull/2002
@DmytroShkvyra Should we support build env such as windows on vm?
---
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
Github user 1ambda commented on the issue:
https://github.com/apache/zeppelin/pull/2002
@DmytroShkvyra Really sorry if you feel like that.
But IMO
- you didn't try almost all possible alternatives
- you didn't try to understand my comments at all. I repeatedly
Github user 1ambda commented on the issue:
https://github.com/apache/zeppelin/pull/2002
@DmytroShkvyra Please read and try #2016
### Details
- yarn installed by frontend-maven-plugin can't run commands described in
scripts tag (package.json)
- but npm is able to
Github user DmytroShkvyra commented on the issue:
https://github.com/apache/zeppelin/pull/2002
@1ambda
>That's cool. You are trying to modify something without understanding.
Anyway, We have 2 problems.
> local development
> you must install yarn if you want to use
Github user 1ambda commented on the issue:
https://github.com/apache/zeppelin/pull/2002
@DmytroShkvyra That's cool. You are trying to modify something without
understanding. Anyway, We have 2 problems.
1. local development
- you must install yarn if you want to use
Github user DmytroShkvyra commented on the issue:
https://github.com/apache/zeppelin/pull/2002
@1ambda
>If you want to use node modules in terminal, you have to install them
globally. (e.g $ yarn install)
>But in case of grunt (and karma so on..), we don't need to do
Github user 1ambda commented on the issue:
https://github.com/apache/zeppelin/pull/2002
@DmytroShkvyra
If you want to use node modules in terminal, you have to install them
globally. (e.g `$ yarn install`)
But in case of grunt (and karma so on..), we don't need to
Github user DmytroShkvyra commented on the issue:
https://github.com/apache/zeppelin/pull/2002
Hi @Leemoonsoo, fontconfig only need to run pahantomjs browser during test
phase of maven build. If you don't want run tests and install fontconfig you
can pass -DSkip.test option to maven
Github user DmytroShkvyra commented on the issue:
https://github.com/apache/zeppelin/pull/2002
All these packages are required and used in scripts of package.json. I
have tested this (run mvn build at clean vbox). And when I tried run
$ npm install -g yarn
$ yarn install
Github user DmytroShkvyra commented on the issue:
https://github.com/apache/zeppelin/pull/2002
@1ambda Seems to Ignite and MR filed. They not related to zeppelin-web.
Is problem in proxy-configuration for bower? I could add support for this
in POM.xml via -D parameters. But I
Github user 1ambda commented on the issue:
https://github.com/apache/zeppelin/pull/2002
FYI - https://github.com/eirslett/frontend-maven-plugin/issues/562
---
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
29 matches
Mail list logo
