Github user asfgit closed the pull request at:
https://github.com/apache/incubator-zeppelin/pull/311
---
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 fea
Hi Dirceu,
Thanks for the feedback.
https://issues.apache.org/jira/browse/ZEPPELIN-269 implements notification
service in front-end. But there're no equivalent part in the back-end side
yet.
If there're some notification service in a back-end side that propagate
messages to front-end, the service
Github user asfgit closed the pull request at:
https://github.com/apache/incubator-zeppelin/pull/317
---
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 fea
Github user Leemoonsoo commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/317#issuecomment-143121374
Looks good to me
---
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 Leemoonsoo commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/319#issuecomment-143106665
Nice improvement.
I think this change does not guarantee message delivery order to the
websocket connection.
How about make `broadcast()` and `bro
Github user corneadoug commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/260#issuecomment-143105625
@prabhjyotsingh Sorry, kinda forgot about this PR being ready.
I see that one test was squashed also what it was testing still exist,
could you fix tha
Github user corneadoug commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/293#issuecomment-143102325
@vinayshukla same steps, with fast click on home after launching the run
all notes
---
If your project is set up for it, you can reply to this email and
Github user prabhjyotsingh commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/260#issuecomment-142972991
@corneadoug @Leemoonsoo do i need to add something as well, or is there a
case that has been missed out ?
---
If your project is set up for it, you c
Github user vinayshukla commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/293#issuecomment-142965751
@corneadoug Hey Doug, Can you please show the steps you took when the
issue is still reproducible?
Did you follow the same steps @prabhjyotsingh too
Rick Moritz created ZEPPELIN-322:
Summary: SparkUI doesn't get killed after test
Key: ZEPPELIN-322
URL: https://issues.apache.org/jira/browse/ZEPPELIN-322
Project: Zeppelin
Issue Type: Bug
Github user RPCMoritz commented on the pull request:
https://github.com/apache/incubator-zeppelin/commit/528dbfaa93fc4e91bf20f30e1498907271073e1a#commitcomment-13412803
In
zeppelin-interpreter/src/test/java/org/apache/zeppelin/scheduler/RemoteSchedulerTest.java:
In
zeppelin-inter
GitHub user RPCMoritz opened a pull request:
https://github.com/apache/incubator-zeppelin/pull/323
[ZEPPELIN-319]wait an additional .5 seconds, if assertion will fail
This test failed randomly during a build. To make sure this is not due to
timing issues, we can optionally wait an a
Github user cloverhearts commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/322#issuecomment-142887892
Thank you answer.
I will make sure you can read it changed.
Have a nice day
---
If your project is set up for it, you can reply to this email a
Github user anthonycorbacho commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/322#issuecomment-142883412
Hi,
nice PR, but can you consider to use momentjs
(http://momentjs.com/docs/#/displaying/fromnow/)?
will same some un necessary code
GitHub user cloverhearts opened a pull request:
https://github.com/apache/incubator-zeppelin/pull/322
The elapsed time is displayed on the notebook list
