You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zeppelin.apache.org by prabhjyotsingh <gi...@git.apache.org> on 2016/06/24 21:01:35 UTC

[GitHub] zeppelin pull request #1086: [Zeppelin 1042] Extra space is present as part ...

GitHub user prabhjyotsingh opened a pull request:

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

    [Zeppelin 1042] Extra space is present as part of username in search box

    ### What is this PR for?
    Sometimes extra space is present as part of username in search box while trying to setup Zeppelin permissions
    
    ### What type of PR is it?
    [Bug Fix]
    
    ### Todos
    * [x] - trim string and then add user
    * [x] - implement searching in Active Directory
    * [x] - improve order by search result
    * [x] - implement debounce to reduce server request
    
    
    ### What is the Jira issue?
    * [ZEPPELIN-1042](https://issues.apache.org/jira/browse/ZEPPELIN-1042)
    
    ### How should this be tested?
    Zeppelin is configured with LDAP authentication.
    Here is the scenario
    
    1. Login as 'user1' user and create a notebook ('Untitled Note 1')
    2. Try to change the permission of 'Untitled Note 1'. Start typing in owners box -> user1
    3. The search box appears with a saved name ' user1' (There is an extra space in front of user1')
    4. Then click on the search box item and save the permissions. The permissions that get saved have all got an extra space before the username 'user1' though it is not intended to have that space.
    5. Later while trying to change the permissions of notebook as 'user1' user, it will disallow because it recognizes ' user1' (user1 with extra space) as owner instead of plain 'user1'
    
    
    ### 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/prabhjyotsingh/zeppelin ZEPPELIN-1042

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

    https://github.com/apache/zeppelin/pull/1086.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 #1086
    
----
commit 179ea7316da4f5ac6b241d3cf985ac6c93a6ca00
Author: Prabhjyot Singh <pr...@gmail.com>
Date:   2016-06-24T19:35:10Z

    enable search for Active Directory

commit d5e5d96af9c10030bc8bf891303859759cd83242
Author: Prabhjyot Singh <pr...@gmail.com>
Date:   2016-06-24T19:35:33Z

    update search preference

commit 57de67fc49de6e74c22d4b77abe7d08a4eb98260
Author: Prabhjyot Singh <pr...@gmail.com>
Date:   2016-06-24T20:05:22Z

    implement debounce

commit a3d5b5c571fd56739028c9ace7926ef54507135e
Author: Prabhjyot Singh <pr...@gmail.com>
Date:   2016-06-24T20:12:13Z

    trim and then add user

----


---
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 #1086: [Zeppelin 1042] Extra space is present as part of user...

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

    https://github.com/apache/zeppelin/pull/1086
  
    Ready for review.
    
    CI fails for  #5337.1. Which is unrelated
    
    ```
    -------------------------------------------------------
     T E S T S
    -------------------------------------------------------
    Running org.apache.zeppelin.python.PythonInterpreterTest
    SLF4J: Class path contains multiple SLF4J bindings.
    SLF4J: Found binding in [jar:file:/home/travis/build/apache/zeppelin/zeppelin-interpreter/target/zeppelin-interpreter-0.6.0-SNAPSHOT.jar!/org/slf4j/impl/StaticLoggerBinder.class]
    SLF4J: Found binding in [jar:file:/home/travis/build/apache/zeppelin/zeppelin-interpreter/target/lib/slf4j-log4j12-1.7.10.jar!/org/slf4j/impl/StaticLoggerBinder.class]
    SLF4J: Found binding in [jar:file:/home/travis/.m2/repository/org/slf4j/slf4j-log4j12/1.7.10/slf4j-log4j12-1.7.10.jar!/org/slf4j/impl/StaticLoggerBinder.class]
    SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
    SLF4J: Actual binding is of type [org.slf4j.impl.Log4jLoggerFactory]
    log4j:WARN No appenders could be found for logger (org.apache.zeppelin.interpreter.Interpreter).
    log4j:WARN Please initialize the log4j system properly.
    log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info.
    Tests run: 5, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.406 sec <<< FAILURE! - in org.apache.zeppelin.python.PythonInterpreterTest
    testClose(org.apache.zeppelin.python.PythonInterpreterTest)  Time elapsed: 0.289 sec  <<< FAILURE!
    java.lang.AssertionError: null
    	at org.junit.Assert.fail(Assert.java:86)
    	at org.junit.Assert.assertTrue(Assert.java:41)
    	at org.junit.Assert.assertFalse(Assert.java:64)
    	at org.junit.Assert.assertFalse(Assert.java:74)
    	at org.apache.zeppelin.python.PythonInterpreterTest.testClose(PythonInterpreterTest.java:168)
    
    
    Results :
    
    Failed tests: 
      PythonInterpreterTest.testClose:168 null
    ```


---
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 #1086: [Zeppelin 1042] Extra space is present as part ...

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

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


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