GitHub user cloverhearts opened a pull request:
https://github.com/apache/zeppelin/pull/1692
[ZEPPELIN-1710 - WIP] Ace Editor upgrade
### What is this PR for?
The current version of the ace editor is too old.
You should also fix a bug that improperly typed non-English typing
Github user agoodm commented on the issue:
https://github.com/apache/zeppelin/pull/1632
@felixcheung @bzz
The final remaining travis error is unrelated, it seems to be occurring
with other recent PRs (https://travis-ci.org/apache/zeppelin/builds/179341529).
Perhaps we should
Github user soralee commented on the issue:
https://github.com/apache/zeppelin/pull/1686
@1ambda Thanks for sharing issue!!
I guess `CTRL+L` short key is being used by some ace editor users.
So, I removed `CTRL-ALT-L` key binding and I changed **Clear output** short
k
Github user AhyoungRyu commented on the issue:
https://github.com/apache/zeppelin/pull/1684
@soralee Thanks for testing it out! Seems it depends on OS as @1ambda said.
LGTM ð
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHu
GitHub user zjffdu opened a pull request:
https://github.com/apache/zeppelin/pull/1691
ZEPPELIN-1716. Error of interpreter not found is not propagated to frâ¦
### What is this PR for?
It is introduced in ZEPPELIN-1399, we call
`InterpreterFactory.getInterpreter` before calling
GitHub user 1ambda opened a pull request:
https://github.com/apache/zeppelin/pull/1690
[ZEPPELIN-1709] docs: Describe how to use checkstyle plugins
### What is this PR for?
The sub issue of https://github.com/apache/zeppelin/pull/1689 (PRs are
splitted due to `contribute.md
Github user khalidhuseynov commented on the issue:
https://github.com/apache/zeppelin/pull/1681
@anthonycorbacho i'll look into this
---
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 featu
Github user soralee commented on the issue:
https://github.com/apache/zeppelin/pull/1684
@marchpig Thanks for this contribution!
I tested it on Ubuntu and It works well!
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as wel
Jeff Zhang created ZEPPELIN-1716:
Summary: Error of interpreter not found is not propagated to
frontend.
Key: ZEPPELIN-1716
URL: https://issues.apache.org/jira/browse/ZEPPELIN-1716
Project: Zeppelin
Github user anthonycorbacho commented on the issue:
https://github.com/apache/zeppelin/pull/1681
Please review otherwise i am merging it
---
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
Github user marchpig commented on the issue:
https://github.com/apache/zeppelin/pull/1684
I've tested it on both Win7 and Ubuntu 12.04.
> Win7 32bit (IE11, Chrome 54.0)
> Ubuntu 12.04 64bit (Firefox 43.0)
This issue only occurred on Ubuntu 12.04 so I think @1ambda's g
Github user zjffdu commented on the issue:
https://github.com/apache/zeppelin/pull/1672
@prabhjyotsingh It works now, but log file permission issue is still here
which make the spark interpreter fail to run unless user manually set permission
---
If your project is set up for it, you
GitHub user agoodm reopened a pull request:
https://github.com/apache/zeppelin/pull/1632
[ZEPPELIN-1639] Add tests with external python dependencies to CI build
### What is this PR for?
Take 2 of #1618 because I had some earlier problems with rebasing. Since,
then I have added s
Github user agoodm closed the pull request at:
https://github.com/apache/zeppelin/pull/1632
---
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 AhyoungRyu commented on the issue:
https://github.com/apache/zeppelin/pull/1684
True. Since both cases (`master` and this patch) are working well for me, I
just wanna know which env can cause this problem.
---
If your project is set up for it, you can reply to this email
Github user cloverhearts commented on the issue:
https://github.com/apache/zeppelin/pull/1637
Okay, fixed all problem.
always ci green
i was change test case for zrun in angular object watch test.
@Leemoonsoo Could you please review for this pr?
---
If your project is set
Github user 1ambda commented on the issue:
https://github.com/apache/zeppelin/pull/1689
Failed due to log size limitation of travis CI
```
The log length has exceeded the limit of 4 MB (this usually means that the
test suite is raising the same exception over and over).
Github user 1ambda commented on the issue:
https://github.com/apache/zeppelin/pull/1684
I am not sure but this might be due to OS
I tested this PR and works well as @marchpig described. (but i didn't
reproduce this issue like @AhyoungRyu)
---
If your project is set up
Github user 1ambda commented on the issue:
https://github.com/apache/zeppelin/pull/1686
Ace users also issued about it. https://github.com/ajaxorg/ace/issues/210
- I think this is a good feature and will be used so many times by so many
people. Thus we should carefully design
Github user 1ambda commented on the issue:
https://github.com/apache/zeppelin/pull/1689
\cc @bzz for review 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 project does not have this feature
enabled and wi
GitHub user 1ambda opened a pull request:
https://github.com/apache/zeppelin/pull/1689
[ZEPPELIN-1709] Update checkstyle rule file, plugin
### What is this PR for?
We have
- outdated checkstyle.xml
- old maven checkstyle plugin
- no detailed style plugin gui
Github user prabhjyotsingh commented on the issue:
https://github.com/apache/zeppelin/pull/1672
This is ready for review, have checked this in few flavours of linux, and
it was working as expected.
---
If your project is set up for it, you can reply to this email and have your
reply
Github user soralee commented on the issue:
https://github.com/apache/zeppelin/pull/1686
@1ambda Thanks for suggestion. :smile:
I tried that but current `CTRL+L` short key is already worked by
editor(ace) as the following picture.
---
If your project is set up for it, you can repl
Github user conker84 commented on the issue:
https://github.com/apache/zeppelin/pull/1582
@felixcheung the CI still fails.
The `org.apache.zeppelin.interpreter.InterpreterOutputChangeWatcherTest`
fails but in my enviroment it passes the test.
Where am i wrong?
---
If your pro
GitHub user krskoondra opened a pull request:
https://github.com/apache/zeppelin/pull/1688
ZEPPELIN-1637 - Add button for "create next block as copy of this block"
### What is this PR for?
Added new buttton "Copy paragraph" near run button. This new button create
copy of current
Github user krskoondra closed the pull request at:
https://github.com/apache/zeppelin/pull/1687
---
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
GitHub user krskoondra opened a pull request:
https://github.com/apache/zeppelin/pull/1687
Branch 0.6
### 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.o
Github user AhyoungRyu commented on the issue:
https://github.com/apache/zeppelin/pull/1647
@Mleekko Thanks for your contribution.
> Since user can choose to run or not to run. Users do not have an option
in current implementation.
And agree with @1ambda :)
LGTM ð
Github user 1ambda commented on the issue:
https://github.com/apache/zeppelin/pull/1686
@soralee This is cool! ð
a small suggestions here :)
- usually, many tools use `CTRL + L` to clear output. Can we use this
familiar key instead?
---
If your project is set
Github user karuppayya commented on the issue:
https://github.com/apache/zeppelin/pull/1678
@Leemoonsoo @zjffdu Ready for 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 karuppayya commented on the issue:
https://github.com/apache/zeppelin/pull/1663
Updated the PR with test @zjffdu
---
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
enab
32 matches
Mail list logo
