Github user mwkang commented on the issue:
https://github.com/apache/zeppelin/pull/1290
I am not sure what is my next step. And this PR was created very long time
ago. So enviroment changed before. I think other contributor can resolve better
than me. So I closed this PR.
Thanks
Github user corneadoug commented on the issue:
https://github.com/apache/zeppelin/pull/1290
@mwkang Just tested quickly, I will have to run more test to check the
behavior in general.
There is some refactoring needed, I left some comments.
Otherwise, a more global
Github user mwkang commented on the issue:
https://github.com/apache/zeppelin/pull/1290
@corneadoug Thanks for your comment. I rebased my branch.
---
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 corneadoug commented on the issue:
https://github.com/apache/zeppelin/pull/1290
@mwkang If you rebase again, the Error 2. Should be fixed.
Error 1. should just be a random one
---
If your project is set up for it, you can reply to this email and have your
reply appear
Github user mwkang commented on the issue:
https://github.com/apache/zeppelin/pull/1290
There are 2 errors.
1. `ZeppelinSparkClusterTest.zRunTest:204 expected: but
was:` does not reproduce.
2.
`AuthenticationIT.testGroupPermission:179->AbstractZeppelinIT.pollingWait:96
Github user corneadoug commented on the issue:
https://github.com/apache/zeppelin/pull/1290
@mwkang Can you rebase please?
---
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 resec commented on the issue:
https://github.com/apache/zeppelin/pull/1290
@mwkang I am excited to see this enhancement implemented, great thanks.
---
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 resec commented on the issue:
https://github.com/apache/zeppelin/pull/1290
@mwkang Just a minor suggestion, when presses and focus
moves to a new cell, is it better that the focused line is next to the [%xxx]?
so users can start typing new code right away without a .
Github user mwkang commented on the issue:
https://github.com/apache/zeppelin/pull/1290
I remove `angular.element('#' + focusedParagraph +
'_paragraphColumn_main').scope().goToLineEnd()`, When paragraph runs.
Because each ace editor keeps cursor position.
So.. user enter
Github user mwkang commented on the issue:
https://github.com/apache/zeppelin/pull/1290
I am not sure. But I think it is persist error.
```
Failed tests:
ParallelSchedulerTest.testRun:63 expected: but was:
```
Anyway.. @Leemoonsoo I change code that it does
Github user mwkang commented on the issue:
https://github.com/apache/zeppelin/pull/1290
I am not sure it is related with this PR.
When I run it, it passed.
```
Failed tests:
ParallelSchedulerTest.testRun:63 expected: but was:
```
---
If your project is set up
Github user mwkang commented on the issue:
https://github.com/apache/zeppelin/pull/1290
I handle that unnecessary persisted in note.json.
I find some problem.
While new paragraph is added in runParagraph, focus is not end of line.
It ignore space character.
Github user Leemoonsoo commented on the issue:
https://github.com/apache/zeppelin/pull/1290
Thanks @mwkang for the contribution. Tested and it works well.
However, i'm not sure about passing informations like "isKeyEvent",
"moveFocusToNextParagraph", etc, through
Github user AhyoungRyu commented on the issue:
https://github.com/apache/zeppelin/pull/1290
@mwkang Thanks for the improvement! Tested locally and it works well as
expected.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user mwkang commented on the issue:
https://github.com/apache/zeppelin/pull/1290
Could you mind if I am going to resolve that consider running paragraph is
successful on new issue?
---
If your project is set up for it, you can reply to this email and have your
reply appear on
15 matches
Mail list logo
