You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zeppelin.apache.org by chiwanpark <gi...@git.apache.org> on 2015/11/11 11:30:01 UTC
[GitHub] incubator-zeppelin pull request: ZEPPELIN-408 Fix configuration bu...
GitHub user chiwanpark opened a pull request:
https://github.com/apache/incubator-zeppelin/pull/420
ZEPPELIN-408 Fix configuration bug of notebook and interpreter directory
Detail description of this issue is in [JIRA](https://issues.apache.org/jira/browse/ZEPPELIN-408). This PR removes some lines of code to set directory configuration in `common.sh`. Although we remove the codes, configuration will be okay because `ZeppelinConfiguration` object has default values.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/chiwanpark/incubator-zeppelin ZEPPELIN-408
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-zeppelin/pull/420.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #420
----
commit 85677e80f5f1c8c3a1d5e3531beee3c3ed98a4fa
Author: Chiwan Park <ch...@icloud.com>
Date: 2015-11-11T10:26:13Z
ZEPPELIN-408 Fix configuration bug of notebook and interpreter directory
----
---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] incubator-zeppelin pull request: ZEPPELIN-408 Fix configuration bu...
Posted by chiwanpark <gi...@git.apache.org>.
Github user chiwanpark commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/420#issuecomment-163228058
@jongyoul I triggered Travis again and got an error in `ZeppelinIT.testAngularDisplay:183`. Is this error relative to this changes?
---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] incubator-zeppelin pull request: ZEPPELIN-408 Fix configuration bu...
Posted by chiwanpark <gi...@git.apache.org>.
Github user chiwanpark closed the pull request at:
https://github.com/apache/incubator-zeppelin/pull/420
---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] incubator-zeppelin pull request: ZEPPELIN-408 Fix configuration bu...
Posted by jongyoul <gi...@git.apache.org>.
Github user jongyoul commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/420#issuecomment-164449569
@chiwanpark Sorry for late reply. I think it would be a kind of flaky test. I'll test this in my local machine.
---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] incubator-zeppelin pull request: ZEPPELIN-408 Fix configuration bu...
Posted by chiwanpark <gi...@git.apache.org>.
Github user chiwanpark commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/420#issuecomment-161931223
Could you guide me to merge this pull request? I couldn't find why CI fails.
---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] incubator-zeppelin pull request: ZEPPELIN-408 Fix configuration bu...
Posted by jongyoul <gi...@git.apache.org>.
Github user jongyoul commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/420#issuecomment-162762341
@chiwanpark It seems like that Spark cluster doesn't run successfully, but I don't know the correct reason because of none of spark's log. Could you please trigger CI again?
---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] incubator-zeppelin pull request: ZEPPELIN-408 Fix configuration bu...
Posted by chiwanpark <gi...@git.apache.org>.
Github user chiwanpark commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/420#issuecomment-186747107
I close this issue due to #731.
---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] incubator-zeppelin pull request: ZEPPELIN-408 Fix configuration bu...
Posted by chiwanpark <gi...@git.apache.org>.
Github user chiwanpark commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/420#issuecomment-164705413
Okay, thanks for testing this PR. Because this PR isn't urgent, you can test this when you have time. :-)
---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---