Github user AhyoungRyu commented on the issue:

    https://github.com/apache/zeppelin/pull/1369
  
    @doanduyhai Sorry for my late response and thanks for the kind reminder.
    I tested again and checked the below issues I mentioned are gone :D
    >(edit interpreter -> add `one:two:1.1.1` to the dependency table -> save )
    Two things are different with master branch. 
    1. Only Spark interpreter throw the ng-toast error message.
    2. The other interpreters' status circle is looping infinitely. It need to 
be reload to turn to red and also don't show the ng-toast error message. 
    
    But I found another issues in the latest update. 
    
    1. edit Alluxio interpreter -> add `aaa:bbb:1.1.1`  to the dependency field 
->  go to another page like "Credential" or "Configuration" -> 
    The `ng-toast` error message is still shown as @astroshim said in the above 
comment. How about adding some timeout property to the message?
    
    2. edit Alluxio -> add `aaa:111:1.1.1` & `bbb:111.2.2.2` to the dependency 
field -> save 
    I think the number of errors and reasons need to be same. Currently, while 
the number of errors keeps increasing whenever I save the change, the only one 
reason "Could not find artifact aaa:111:jar:1.1.1 in central 
(http://repo1.maven.org/maven2/)" is shown. Need to show "Could not find 
artifact bbb:111.2.2.2 in central (http://repo1.maven.org/maven2/)" as well if 
we want to show the number of errors. 
    
    <img width="1263" alt="screen shot 2016-09-18 at 9 37 55 pm" 
src="https://cloud.githubusercontent.com/assets/10060731/18615730/026b5b42-7de9-11e6-9294-c8a88687f896.png";>
    
    The number of error should be 2 in the above case I guess. But as you can 
see the number is 1 since `checkDownloadingDependencies()` is called only one 
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Reply via email to