Github user AlexanderShoshin closed the pull request at:
https://github.com/apache/zeppelin/pull/2206
---
Github user jongyoul commented on the issue:
https://github.com/apache/zeppelin/pull/2206
Can you fix it to fit with current master as well?
---
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
Github user AlexanderShoshin commented on the issue:
https://github.com/apache/zeppelin/pull/2206
@jongyoul it looks like I need to correct my unit tests due last changes in
master
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub
Github user jongyoul commented on the issue:
https://github.com/apache/zeppelin/pull/2206
@AlexanderShoshin Can you rebase it from current master?
---
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
Github user AlexanderShoshin commented on the issue:
https://github.com/apache/zeppelin/pull/2206
Hi @jongyoul,
I've added a test for my changes but it won't run until we restore second
Travis job which should start all core tests.
I will write when the test will be able to
Github user AlexanderShoshin commented on the issue:
https://github.com/apache/zeppelin/pull/2206
Sure, I'll do it.
But first I need to make some refactoring of `Note.java` class in separate
PR. We need to be able to add a custom `Paragraph` to `Note`. This will allow
to use a
Github user jongyoul commented on the issue:
https://github.com/apache/zeppelin/pull/2206
Can you make a test in case OUTPUT_UPDATE_ALL is passed after job is done?
---
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
GitHub user AlexanderShoshin opened a pull request:
https://github.com/apache/zeppelin/pull/2206
[ZEPPELIN-1856] Flaky Test:
InterpreterRestApiTest.testRestartInterpreterPerNote
### What is this PR for?
A _NullPointerException_ occurs occasionally
TE events as well?
>
> Regards,
> Alexander
>
> -Original Message-
> From: moon soo Lee [mailto:m...@apache.org]
> Sent: Tuesday, February 07, 2017 8:28 AM
> To: dev@zeppelin.apache.org
> Subject: Re: ZEPPELIN-1856
>
> onOutputClear() method is connected with
interpreter.
Should we ignore latecomer OUTPUT_APPEND and OUTPUT_UPDATE events as well?
Regards,
Alexander
-Original Message-
From: moon soo Lee [mailto:m...@apache.org]
Sent: Tuesday, February 07, 2017 8:28 AM
To: dev@zeppelin.apache.org
Subject: Re: ZEPPELIN-1856
onOutputClear
HED status we will come in
> situation where we always clear an empty 'Paragraph.results'. Does it make
> sense?
>
> Regards,
> Alexander
>
> -Original Message-
> From: moon soo Lee [mailto:m...@apache.org]
> Sent: Saturday, February 04, 2017 4:30 AM
> To: d
To: dev@zeppelin.apache.org
Subject: Re: ZEPPELIN-1856
Hi,
Thanks for working on issue ZEPPELIN-1856.
I think removing 'note.clearParagraphOutput(paragraphId);' from
'onOutputClear()' is not the best solution, because without the line
'onOutputClear()' does not do anything useful
Hi,
Thanks for working on issue ZEPPELIN-1856.
I think removing 'note.clearParagraphOutput(paragraphId);' from
'onOutputClear()' is not the best solution, because without the line
'onOutputClear()' does not do anything useful.
InterpreterContext is constructed before call
Hi,
I'm working on issue https://issues.apache.org/jira/browse/ZEPPELIN-1856 and I
found that we receive a NullPointerException sometimes because a paragraph
result is cleared twice when we run a job. First Paragraph.result is cleared
just before running RemoteInterpreter.interpret
Le ven. 23 déc. 2016 à 17:48, Hoon Park (JIRA) <j...@apache.org> a écrit :
> Hoon Park created ZEPPELIN-1856:
>
> ---
>
>
>
> Summary: Flaky Test:
> InterpreterRestApiTest.testRestartInterpreterPerNote
>
>
Hoon Park created ZEPPELIN-1856:
---
Summary: Flaky Test:
InterpreterRestApiTest.testRestartInterpreterPerNote
Key: ZEPPELIN-1856
URL: https://issues.apache.org/jira/browse/ZEPPELIN-1856
Project: Zeppelin
16 matches
Mail list logo
