Github user doanduyhai commented on the issue:
https://github.com/apache/zeppelin/pull/1369
@AhyoungRyu
> The ng-toast error message is still shown as @astroshim said in the above
comment. How about adding some timeout property to the message?
I knew that there is a timeout option for `ng-toast` but I chose not use
it. The simple reason is that I consider the dependency issue is a **serious**
issue so we want the user to **explicitly/manually** close the error popup and
acknowledge that he is aware about the download issue.
What is your opinion about that ? Adding a timeout to automatically close
the error popup is very easy.
> 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.
There is a simple explanation for this. `sonatye.aether` library tries to
download the dependencies **one after another** and raise an exception as soon
as it cannot find/download a dependency. In your example, we'll see the error
popup for the 2<sup>nd</sup> dependency if the download of the 1<sup>st</sup>
is successful
```java
synchronized (repos) {
for (RemoteRepository repo : repos) {
collectRequest.addRepository(repo);
}
}
DependencyRequest dependencyRequest = new
DependencyRequest(collectRequest,
DependencyFilterUtils.andFilter(exclusionFilter,
classpathFilter));
try {
return system.resolveDependencies(session,
dependencyRequest).getArtifactResults();
} catch (NullPointerException ex) {
throw new RepositoryException(String.format("Cannot fetch
dependencies for %s", dependency));
}
```
We cannot change the behavior of `sonatype.aether`. We can change our
source code to download dependency **one by one** but it is very slow and
require changing the interface of a lot of methods
---
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.
---
