GitHub user vistep opened a pull request:

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

    [ZEPPELIN-2841] fix a problem in shell interpreter . Working directory '.' 
can not be found in docker envi

    ### What is this PR for?
    shell interpreter complained that working directory '.' can not be found in 
docker environment.
    I add a line of code to set current working directory to USER`s home, and 
it works.
    
    
    ### What type of PR is it?
    Bug Fix
    
    ### Todos
    * tests
    
    ### What is the Jira issue?
    https://issues.apache.org/jira/browse/ZEPPELIN-2841
    * Open an issue on Jira https://issues.apache.org/jira/browse/ZEPPELIN/
    * Put link here, and add [ZEPPELIN-*Jira number*] in PR title, eg. 
[ZEPPELIN-533]
    
    ### How should this be tested?
    Outline the steps to test the PR here.
    
    ### Screenshots (if appropriate)
    
    ### Questions:
    * Does the licenses files need update?
    * Is there breaking changes for older versions?
    * Does this needs documentation?

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

    $ git pull https://github.com/vistep/zeppelin master

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

    https://github.com/apache/zeppelin/pull/2521.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 #2521
    
----
commit d02104ac58a85e6e70704a57ed43ae6a32bb0b61
Author: 束佳明 <shujiam...@hotmail.com>
Date:   2017-08-05T07:50:50Z

    Merge pull request #1 from apache/master
    
    merge apache/zeppelin

commit e8cbdd180a22d1d53366c94c5432c217d70a5727
Author: Shu Jiaming <jiaming....@transwarp.io>
Date:   2017-08-08T16:25:15Z

    ZEPPELIN-2841 fix a bug where shell interpreter complained that working 
directory '.' cna not be found in docker enviroment.

----


---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Reply via email to