jasmine song created ZEPPELIN-5682:
--
Summary: Monaco-Editor Some keywords are not highlighted
Key: ZEPPELIN-5682
URL: https://issues.apache.org/jira/browse/ZEPPELIN-5682
Project: Zeppelin
Is
zjffdu merged pull request #4310:
URL: https://github.com/apache/zeppelin/pull/4310
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscr..
pjfanning opened a new pull request #4315:
URL: https://github.com/apache/zeppelin/pull/4315
### What is this PR for?
A few sentences describing the overall goals of the pull request's commits.
First time? Check out the contributing guide -
https://zeppelin.apache.org/contribution/con
pjfanning closed pull request #4296:
URL: https://github.com/apache/zeppelin/pull/4296
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubsc
pjfanning commented on pull request #4296:
URL: https://github.com/apache/zeppelin/pull/4296#issuecomment-1069035366
closing in favour of https://github.com/apache/zeppelin/pull/4315
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to G
pjfanning opened a new pull request #4316:
URL: https://github.com/apache/zeppelin/pull/4316
### What is this PR for?
https://mvnrepository.com/artifact/org.bouncycastle/bcprov-jdk15on shows the
CVE
Related to https://issues.apache.org/jira/browse/ZEPPELIN-4657
zjffdu commented on pull request #4315:
URL: https://github.com/apache/zeppelin/pull/4315#issuecomment-1069175049
Thanks @pjfanning Could you update the PR description?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use
zjffdu merged pull request #4311:
URL: https://github.com/apache/zeppelin/pull/4311
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscr..
pjfanning commented on pull request #4315:
URL: https://github.com/apache/zeppelin/pull/4315#issuecomment-1069177313
@zjffdu is the change I made to the PR description ok?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and u
PJ Fanning created ZEPPELIN-5683:
Summary: upgrade commons-compress and commons-io due to CVEs
Key: ZEPPELIN-5683
URL: https://issues.apache.org/jira/browse/ZEPPELIN-5683
Project: Zeppelin
Is
zjffdu edited a comment on pull request #4315:
URL: https://github.com/apache/zeppelin/pull/4315#issuecomment-1069182393
@pjfanning PR description LGTM, but could you create a separate jira ticket
for it? Usually, each PR is associated with one jira ticket. You can create
ticket under
[ZE
PJ Fanning created ZEPPELIN-5684:
Summary: upgrade bouncycastle due to cve
Key: ZEPPELIN-5684
URL: https://issues.apache.org/jira/browse/ZEPPELIN-5684
Project: Zeppelin
Issue Type: Bug
zjffdu commented on pull request #4315:
URL: https://github.com/apache/zeppelin/pull/4315#issuecomment-1069182393
@pjfanning PR description LGTM, but could you create a separate jira ticket
for it? Usually, each PR is associated with one jira ticket. You can create
ticket under
[ZEPPELIN-
pjfanning commented on pull request #4315:
URL: https://github.com/apache/zeppelin/pull/4315#issuecomment-1069187577
I created ZEPPELIN-5683
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the s
zjffdu commented on pull request #4315:
URL: https://github.com/apache/zeppelin/pull/4315#issuecomment-1069190418
PR LGTM, thanks @pjfanning
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the
zjffdu commented on pull request #4294:
URL: https://github.com/apache/zeppelin/pull/4294#issuecomment-1069194549
@saLeox Could you do a rebase and trigger CI again?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
PJ Fanning created ZEPPELIN-5685:
Summary: upgrade shiro
Key: ZEPPELIN-5685
URL: https://issues.apache.org/jira/browse/ZEPPELIN-5685
Project: Zeppelin
Issue Type: Sub-task
Reporte
pjfanning opened a new pull request #4317:
URL: https://github.com/apache/zeppelin/pull/4317
### What is this PR for?
https://issues.apache.org/jira/browse/ZEPPELIN-5685
Security concern over existing jar
### What type of PR is it?
Bug Fix
### Todos
* [
saLeox commented on pull request #4294:
URL: https://github.com/apache/zeppelin/pull/4294#issuecomment-1069213561
@zjffdu Done, and pls help approve the new CI
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL a
zjffdu commented on pull request #4294:
URL: https://github.com/apache/zeppelin/pull/4294#issuecomment-1069821006
CI is passed, will merge if no more comment
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL abo
zjffdu opened a new pull request #4318:
URL: https://github.com/apache/zeppelin/pull/4318
### What is this PR for?
The issue is that when interpreter process is shut down abnormally,
zeppelin-server doesn't know that, and still try to call thrift api. This
introduce `RemoteCallExcep
21 matches
Mail list logo
