You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zeppelin.apache.org by Leemoonsoo <gi...@git.apache.org> on 2015/07/03 00:12:41 UTC

[GitHub] incubator-zeppelin pull request: [WIP] ZEPPELIN-152 Propagate erro...

GitHub user Leemoonsoo opened a pull request:

    https://github.com/apache/incubator-zeppelin/pull/136

    [WIP] ZEPPELIN-152 Propagate error from interpreter process to the GUI

    https://issues.apache.org/jira/browse/ZEPPELIN-152
    Errors from remote process are not propagated correctly. So, before go and check interpreter's log, it's hard to see actual problem.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/Leemoonsoo/incubator-zeppelin ZEPPELIN-152

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/incubator-zeppelin/pull/136.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 #136
    
----
commit 19cfc449b4d0882fcb1f44b75b1fe92680e6e724
Author: Lee moon soo <mo...@apache.org>
Date:   2015-07-02T22:10:56Z

    Propagte remote process's exception

commit 34a02103c9ccb368a9d240cdd74e73aa087aa1d0
Author: Lee moon soo <mo...@apache.org>
Date:   2015-07-02T22:11:21Z

    Let exception goes

----


---
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: [WIP] ZEPPELIN-152 Propagate erro...

Posted by Leemoonsoo <gi...@git.apache.org>.
Github user Leemoonsoo commented on the pull request:

    https://github.com/apache/incubator-zeppelin/pull/136#issuecomment-118412891
  
    This will change propagate error message and status from remote interpreter to the front-end. For example, 
    
    before
    ![image](https://cloud.githubusercontent.com/assets/1540981/8504032/8a9ebd10-217e-11e5-9780-129ae228f1c3.png)
    
    after
    ![image](https://cloud.githubusercontent.com/assets/1540981/8503987/ad192836-217d-11e5-8563-cdb6e6b1649f.png)
    
    Ready to merge


---
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-152 Propagate error from...

Posted by Leemoonsoo <gi...@git.apache.org>.
Github user Leemoonsoo commented on the pull request:

    https://github.com/apache/incubator-zeppelin/pull/136#issuecomment-118540599
  
    Merging if there're no more discussions.


---
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-152 Propagate error from...

Posted by asfgit <gi...@git.apache.org>.
Github user asfgit closed the pull request at:

    https://github.com/apache/incubator-zeppelin/pull/136


---
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.
---