GitHub user cloverhearts reopened a pull request:
https://github.com/apache/zeppelin/pull/1864
[ZEPPELIN-1921] missing close in closeAndRemoveInterpreterGroup method
### What is this PR for?
The problem is that some code in the closeAndRemoveInterpreterGroup method
of Interprete
Github user cloverhearts closed the pull request at:
https://github.com/apache/zeppelin/pull/1864
---
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 featur
Github user soralee commented on the issue:
https://github.com/apache/zeppelin/pull/1892
@minahlee I updated and resolved another way.
When web application develop mode, the source base of production mode is
different to web application develop mode. So, I updated to correct source
GitHub user DrIgor opened a pull request:
https://github.com/apache/zeppelin/pull/1911
[ZEPPELIN-1972] Preserve context classloader
### What is this PR for?
`IMain.interpret` changes current thread's context classloader. It may
cause different issues and definitely is the reason
Github user zjffdu commented on the issue:
https://github.com/apache/zeppelin/pull/1910
@Leemoonsoo @jongyoul Please help review.
---
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
Github user Leemoonsoo commented on the issue:
https://github.com/apache/zeppelin/pull/1910
LGTM
---
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
Github user jongyoul commented on the issue:
https://github.com/apache/zeppelin/pull/1910
LGTM
---
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 f
Github user jongyoul commented on the issue:
https://github.com/apache/zeppelin/pull/1911
LGMT. I have a question. Is there any related issue to SparkInterpreter?
Can you take a look into it?
---
If your project is set up for it, you can reply to this email and have your
reply appear
Github user jongyoul commented on the issue:
https://github.com/apache/zeppelin/pull/1864
@cloverhearts the failed test looks related this patch. Can you check it?
```
Failed tests:
NoteInterpreterLoaderTest.testNoteInterpreterCloseForAll:192 null
```
---
If yo
Hello, fellow Apache enthusiast. Thanks for your participation, and
interest in, the projects of the Apache Software Foundation.
I wanted to remind you that the Call For Papers (CFP) for ApacheCon
North America, and Apache: Big Data North America, closes in less than a
month. If you've been puttin
I'd agree. Is there a course of actions you can propose? Disable all these
tests is a not a long term solution, right?
_
From: Jeff Zhang mailto:zjf...@gmail.com>>
Sent: Tuesday, January 17, 2017 6:01 PM
Subject: Re: Unstable travis CI recently
To: mailto:dev@zeppelin
I also agree that ppl don't care of the result of CI anymore even it's real
failure. One possible solution is making umbrella ticket, grabbing flaky
tests, disabling at first and enabling when it solves. but it assumes we
need to do our best to fix the flaky tests. Otherwise, we will lose some
test
Github user asfgit closed the pull request at:
https://github.com/apache/zeppelin/pull/1883
---
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 e
Github user jongyoul commented on the issue:
https://github.com/apache/zeppelin/pull/1902
@1ambda Can you review this PR deeply?
---
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
e
Ruslan Dautkhanov created ZEPPELIN-1979:
---
Summary: 'File size limit Exceeded' when importing notes - even
for small files
Key: ZEPPELIN-1979
URL: https://issues.apache.org/jira/browse/ZEPPELIN-1979
Alex Goodman created ZEPPELIN-1980:
--
Summary: Test and update CI for matplotlib 2.0.0
Key: ZEPPELIN-1980
URL: https://issues.apache.org/jira/browse/ZEPPELIN-1980
Project: Zeppelin
Issue Type
GitHub user agoodm opened a pull request:
https://github.com/apache/zeppelin/pull/1912
[HOTFIX][ZEPPELIN-1980] - Test and update CI for matplotlib 2.0.0
### What is this PR for?
Matplotlib 2.0.0 was just released. It has introduced some major changes
including some to the `rcPar
+1
Best Regard,
Jeff Zhang
On 1/19/17, 1:03 AM, "Jongyoul Lee" wrote:
>I also agree that ppl don't care of the result of CI anymore even it's
>real
>failure. One possible solution is making umbrella ticket, grabbing flaky
>tests, disabling at first and enabling when it solves. but it assum
Github user asfgit closed the pull request at:
https://github.com/apache/zeppelin/pull/1782
---
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 e
Github user Leemoonsoo commented on the issue:
https://github.com/apache/zeppelin/pull/1910
Merge to master and branch-0.7
---
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
Jongyoul Lee created ZEPPELIN-1981:
--
Summary: Fix all flaky tests
Key: ZEPPELIN-1981
URL: https://issues.apache.org/jira/browse/ZEPPELIN-1981
Project: Zeppelin
Issue Type: Task
R
Thanks Jeff,
I made a new PR for handling this issue.
https://issues.apache.org/jira/browse/ZEPPELIN-1981
On Thu, Jan 19, 2017 at 9:47 AM, Jianfeng (Jeff) Zhang <
jzh...@hortonworks.com> wrote:
> +1
>
> Best Regard,
> Jeff Zhang
>
>
>
>
>
> On 1/19/17, 1:03 AM, "Jongyoul Lee" wrote:
>
> >I als
Github user asfgit closed the pull request at:
https://github.com/apache/zeppelin/pull/1906
---
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 e
GitHub user khalidhuseynov opened a pull request:
https://github.com/apache/zeppelin/pull/1913
[ZEPPELIN-1979] fix 'File size limit Exceeded' when importing notes
### What is this PR for?
This is to fix the problem with import of note because of size limitations.
Actually it see
Hi Jongyoul,
Could you move all these tickets under this umbrella ticket ?
You can do bulk change by clicking the gear tool button on top right of
this page. ( I don't' have privilege to do that)
https://issues.apache.org/jira/issues/?jql=project%20%3D%20ZEPPELIN%20AND%20text%20~%20flaky%20and%
25 matches
Mail list logo
