You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zeppelin.apache.org by SachinJanani <gi...@git.apache.org> on 2016/07/27 06:41:43 UTC

[GitHub] zeppelin pull request #1234: [ZEPPELIN-1234] Fix for bug ZEPPELIN-1234

GitHub user SachinJanani opened a pull request:

    https://github.com/apache/zeppelin/pull/1234

    [ZEPPELIN-1234] Fix for bug ZEPPELIN-1234

    ### What is this PR for?
    A few sentences describing the overall goals of the pull request's commits.
    First time? Check out the contributing guide - https://github.com/apache/zeppelin/blob/master/CONTRIBUTING.md
    
    
    ### What type of PR is it?
    Bug fix
    
    ### Todos
    * [ ] - NA
    
    ### What is the Jira issue?
    * https://issues.apache.org/jira/browse/ZEPPELIN-1234
    
    ### How should this be tested?
    -Create a remote interpreter,start and connect it as mentioned in doc http://zeppelin.apache.org/docs/0.6.0/manual/interpreters.html#connecting-to-the-existing-remote-interpreter
    - Try to restart the interpreter
    
    ### Screenshots (if appropriate)
    
    ### Questions:
    * Does the licenses files need update? No
    * Is there breaking changes for older versions? No
    * Does this needs documentation? No
    


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

    $ git pull https://github.com/SachinJanani/zeppelin branch-0.6

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

    https://github.com/apache/zeppelin/pull/1234.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 #1234
    
----
commit 8688548ee8ab49482e0c1d0319dbef93b1427583
Author: Sachin <sj...@snappydata.io>
Date:   2016-07-27T06:33:46Z

    [ZEPPELIN-1234] Fix for bug ZEPPELIN-1234

----


---
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] zeppelin issue #1234: [ZEPPELIN-1234] Fix for bug ZEPPELIN-1234

Posted by SachinJanani <gi...@git.apache.org>.
Github user SachinJanani commented on the issue:

    https://github.com/apache/zeppelin/pull/1234
  
    Failure of travis check is not related to this change


---
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] zeppelin pull request #1234: [ZEPPELIN-1234] Fix issue related to indefinite...

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

    https://github.com/apache/zeppelin/pull/1234


---
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] zeppelin issue #1234: [ZEPPELIN-1234] Fix for bug ZEPPELIN-1234

Posted by jongyoul <gi...@git.apache.org>.
Github user jongyoul commented on the issue:

    https://github.com/apache/zeppelin/pull/1234
  
    @SachinJanani Could you please add test case for this bug? It would help understand the situation.


---
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] zeppelin issue #1234: [ZEPPELIN-1234] Fix issue related to indefinite waitin...

Posted by jongyoul <gi...@git.apache.org>.
Github user jongyoul commented on the issue:

    https://github.com/apache/zeppelin/pull/1234
  
    @SachinJanani Thanks for doing it.


---
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] zeppelin issue #1234: [ZEPPELIN-1234] Fix for bug ZEPPELIN-1234

Posted by SachinJanani <gi...@git.apache.org>.
Github user SachinJanani commented on the issue:

    https://github.com/apache/zeppelin/pull/1234
  
    Travis checks are failing but are not related to this changes.@jongyoul Can you please have a look. 


---
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] zeppelin issue #1234: [ZEPPELIN-1234] Fix for bug ZEPPELIN-1234

Posted by jongyoul <gi...@git.apache.org>.
Github user jongyoul commented on the issue:

    https://github.com/apache/zeppelin/pull/1234
  
    I've tested it. LGTM. merging if there's no more discussion.


---
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] zeppelin issue #1234: [ZEPPELIN-1234] Fix issue related to indefinite waitin...

Posted by SachinJanani <gi...@git.apache.org>.
Github user SachinJanani commented on the issue:

    https://github.com/apache/zeppelin/pull/1234
  
    @jongyoul Sure I will close it now.Thanks 


---
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] zeppelin issue #1234: [ZEPPELIN-1234] Fix for bug ZEPPELIN-1234

Posted by jongyoul <gi...@git.apache.org>.
Github user jongyoul commented on the issue:

    https://github.com/apache/zeppelin/pull/1234
  
    @SachinJanani Could you please revise the title of this PR? The title will be the first commit message and I think you need to revise them.


---
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] zeppelin issue #1234: [ZEPPELIN-1234] Fix issue related to indefinite waitin...

Posted by jongyoul <gi...@git.apache.org>.
Github user jongyoul commented on the issue:

    https://github.com/apache/zeppelin/pull/1234
  
    @SachinJanani This PR is merged into branch-0.6 but I think you will close this PR by yourself because this is not merged into master. Can you do it?


---
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] zeppelin issue #1234: [ZEPPELIN-1234] Fix issue related to indefinite waitin...

Posted by SachinJanani <gi...@git.apache.org>.
Github user SachinJanani commented on the issue:

    https://github.com/apache/zeppelin/pull/1234
  
    @jongyoul I revised the PR title and its description


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