GitHub user prabhjyotsingh opened a pull request:
https://github.com/apache/zeppelin/pull/3114
Update org.eclipse.jetty version to 9.4.11.v20180605 to avoid CVE issues
### What is this PR for?
Update org.eclipse.jetty version to 9.4.11.v20180605 to avoid CVE issues.
See
Prabhjyot Singh created ZEPPELIN-3686:
-
Summary: Update org.eclipse.jetty version to 9.4.11.v20180605 to
avoid CVE issues
Key: ZEPPELIN-3686
URL: https://issues.apache.org/jira/browse/ZEPPELIN-3686
Github user zjffdu commented on the issue:
https://github.com/apache/zeppelin/pull/3092
Thanks @selvinsource for the investigation, the analysis seems correct to
me.
---
Github user zjffdu commented on the issue:
https://github.com/apache/zeppelin/pull/3054
CI pass, will merge if no more comments
---
Github user zjffdu commented on the issue:
https://github.com/apache/zeppelin/pull/3111
@egorklimov Did you configure travis ?
---
Github user selvinsource commented on the issue:
https://github.com/apache/zeppelin/pull/3092
Found something that could cause the issue.
in beam/pom.xml there is
```2.0.0```
then
```
beam-runners-flink_${scala.binary.version}```
But looking at
Github user selvinsource commented on the issue:
https://github.com/apache/zeppelin/pull/3092
@zjffdu @mebelousov I sent you a comment before, please ignore, I thought
that scio was only built for 2.10 but I noticed that changing scala version
using the script does update the pom for
Github user selvinsource commented on the issue:
https://github.com/apache/zeppelin/pull/3092
@zjffdu
the issue reported by @mebelousov may have been caused by
https://issues.apache.org/jira/browse/ZEPPELIN-3557
and not this PR, as I only added in the beam interpreter the
Github user selvinsource commented on the issue:
https://github.com/apache/zeppelin/pull/3092
@mebelousov
If you see
https://travis-ci.org/selvinsource/zeppelin/builds/411153675
it seems fine with SCALA_VER="2.11".
What options are you running maven build
Github user egorklimov commented on the issue:
https://github.com/apache/zeppelin/pull/3107
@felixcheung On other hand, risk of showing all notes may be greater,
therefore I think that we should add this workaround, because everyone who is
upgrading from any version less than 0.8.x
Michael Williams created ZEPPELIN-3685:
--
Summary: Graphs drawn incorrectly
Key: ZEPPELIN-3685
URL: https://issues.apache.org/jira/browse/ZEPPELIN-3685
Project: Zeppelin
Issue Type: Bug
Github user mebelousov closed the pull request at:
https://github.com/apache/zeppelin/pull/3081
---
Github user mebelousov commented on the issue:
https://github.com/apache/zeppelin/pull/3081
Will try to revert with tests.
---
GitHub user Savalek opened a pull request:
https://github.com/apache/zeppelin/pull/3113
[ZEPPELIN-3616] fix editor sections auto-collapse
# Description
This PR change logic of add new event listener on frontend. Now then add
new event listener, also added destroy listener.
GitHub user GioCorti80 opened a pull request:
https://github.com/apache/zeppelin/pull/3112
Branch 0.8
### What is this PR for?
Problem on command: docker pull apache/zeppelin
### What type of PR is it?
[Bug]
i receive this error: "Error response from
GitHub user egorklimov opened a pull request:
https://github.com/apache/zeppelin/pull/3111
testCronDisable fixed
### What is this PR for?
`testCronDisable` in `ZeppelinRestApiTest` produce error:
```
09:15:51,001 ERROR org.quartz.core.ErrorLogger:2425 - Job
Github user mebelousov commented on the issue:
https://github.com/apache/zeppelin/pull/3092
Seems this PR broke build for scala 2.11
After execution of ` ./dev/change_scala_version.sh 2.11` I have got error
```
[ERROR] Failed to execute goal on project zeppelin-beam:
George Klimov created ZEPPELIN-3684:
---
Summary: Remove cron job in ZeppelinRestApiTest.testCronDisable
Key: ZEPPELIN-3684
URL: https://issues.apache.org/jira/browse/ZEPPELIN-3684
Project: Zeppelin
18 matches
Mail list logo
