Randy Gelhausen created ZEPPELIN-780:
Summary: For interpreters with multiple %types, allow re-ordering
of types
Key: ZEPPELIN-780
URL: https://issues.apache.org/jira/browse/ZEPPELIN-780
Project:
Github user bzz commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/807#issuecomment-203761293
Looks great to me :shipit:
---
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
Github user elbamos commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/208#issuecomment-203756326
@bzz I think I've just done what you requested.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as we
Guys, please note the subj change.
I think we are almost there with PR 208, there are very few things now that
we are working out to finish, the progress is tracked at [1]
Please let me look into ZEPPELIN-776 [2] more - it looks very strange
indeed.
It does not look like code in 208 affects pyspa
Github user bzz commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/208#issuecomment-203753693
@elbamos I'm sorry for a confusion! I was basically asking you to post same
replies that you did before, but in the places where I have posted the
questions - co
Github user elbamos commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/208#issuecomment-203751439
@bzz I'm not questioning the wisdom of why you're asking me what to do what
you're asking -- I just literally do not understand what you're asking. When
you'
Github user bzz commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/208#issuecomment-203749879
@elbamos :+1: for keeping the docs update! Yes, I believe licenses for each
contributed file are clear now, but what I was asking you for is just to follow
each
Github user mwkang commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/806#issuecomment-203746988
@Leemoonsoo
I change some code. Could you mind if I request to review this?
---
If your project is set up for it, you can reply to this email and have yo
Github user elbamos commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/208#issuecomment-203733605
@jeffsteinmetz I just pushed the fixed screenshots. Thanks, by the way,
for asking that the show functions be taken out --- I can see that the
`googleVis` p
Github user elbamos commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/208#issuecomment-203731211
@bzz I'm not sure I understand what you're requesting -- but in any event,
I think the issue for right now is resolved, correct?
---
If your project is set
Github user bzz commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/208#issuecomment-203730593
@elbamos got it, but could you please post your answers in the comments
that I have made, and linked from the list, so we have full conversation
history online?
Github user jeffsteinmetz commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/208#issuecomment-203726976
The `.z.show.googleVis` etc.
---
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 pr
Github user elbamos commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/208#issuecomment-203726914
Ah - you mean because I took out the show() functions yesterday in respect
of your comment about that.
---
If your project is set up for it, you can reply
Github user elbamos commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/208#issuecomment-203726802
@jeffsteinmetz Can you be more specific? Do you mean because they refer to
%spark.r and %spark.knitr?
---
If your project is set up for it, you can reply
Github user jeffsteinmetz commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/208#issuecomment-203726463
re Docs: I noticed this `docs/interpreter/screenshots/knitmotion.png` and a
few other screen shots no longer reflect the current implementation.
---
I
Github user elbamos commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/208#issuecomment-203726453
@bzz I just looked at the list, and its all the same thing. I took out of
rscala the code for making an R->scala connection. There isn't anything new
added
Github user bzz commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/208#issuecomment-203726149
@elbamos sure, now I have updated list in
https://github.com/apache/incubator-zeppelin/pull/208#issuecomment-203673589
could you please clarify few question left
Github user elbamos commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/208#issuecomment-203722796
@bzz Thank you for catching RException - I have taken out the reference to
DDahl.
I don't think this is that complicated:
* RClient.scala --- M
Edwin Shin created ZEPPELIN-779:
---
Summary: Error creating dynamic select form in Python
Key: ZEPPELIN-779
URL: https://issues.apache.org/jira/browse/ZEPPELIN-779
Project: Zeppelin
Issue Type: B
Github user bzz commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/208#issuecomment-203721628
@elbamos I have create file list and updated comment above to track our
progress
https://github.com/apache/incubator-zeppelin/pull/208#issuecomment-203673589
Github user bzz commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/208#issuecomment-203718108
On RException - then please feel free to remove `//Originally by David Dahl
and released under the BSD license` if that is your contribution.
> Meanwhile
Github user elbamos commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/208#issuecomment-203714774
@bzz - The test is back in with @ignore, and CI is green. Do you have a
decision on the license files?
---
If your project is set up for it, you can reply
Github user mwkang commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/806#issuecomment-203707670
I agree with you. This commit is too hasty.
I'm so sorry. I'm looking in that.
---
If your project is set up for it, you can reply to this email and have
Github user elbamos commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/208#issuecomment-203698160
@bzz - that's basically the list for scala files, except that I'm pretty
sure RException was mine. The other thing is the R source. The rzeppelin.R is
mine
Github user bzz commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/208#issuecomment-203693548
@elbamos right, I'm looking into licenses and will post back soon.
Meanwhile can you please help providing the list of such files to save the time
identifying th
Github user elbamos commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/208#issuecomment-203684695
@bzz I will look into junit ignore. Regarding the licenses, that issue is
where it has been: For files that are forked from other things, but also
contain
Github user Leemoonsoo commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/806#issuecomment-203682574
Zeppelin automatically adds new paragraph when last paragraph runs.
Isn't it make sense to add %.* to this auto added paragraph?
---
If your project i
Github user Leemoonsoo commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/751#issuecomment-203680939
Merge into master if there're no more discussions
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub a
Github user Leemoonsoo commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/702#issuecomment-203680677
Merge into master if there're no more discussions
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub a
Github user bzz commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/208#issuecomment-203673589
Great!
Here is the list of things that need to be done in order to merge this PR:
- [x] ~~master and this branch have diverged: we need to either mer
Amos
"When it tries that, in some spark configurations it can't verify that the
cluster is up, so it never runs its tests."
--> Precisely, once every time I looked into the detailed Travis log, one
of the reason the cluster is not up was that the Travis server/VM/container
has not enough resource
Github user jeffsteinmetz commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/702#issuecomment-203538247
Looks great.
I just fired up a spark cluster on EC2 using the spark Amazon ec2 scripts.
Pointed zeppelin to the cluster master running 3 nodes.
DuyHai - I'm not sure we're talking about exactly the same thing.
There is one issue which is that CI just sort of randomly fails, for
example last night many times when it was supposed to download Spark, the
spark .tar.gz file failed on checksum. This was just random. I was able
to resolve the
Amos
"It's also not correct to say that the test class even "fails" -- what's
happening is that the testing infrastructure for this class fails to load."
--> This is the behavior I have observed many many times
Being a heavy user of Travis (see my other open source project
www.achilles.io) I can
Amos,
Please respect the community consensus [1] and author of 702 and people
collaborated in 702. They're all community members.
Like i summarized
http://apache-zeppelin-incubating-dev-mailing-list.75694.x6.nabble.com/DISCUSS-Back-to-PRs-208-702-tp7691p7787.html,
no one disagree on 702.
And ple
Oliver Drewes created ZEPPELIN-778:
--
Summary: Hotkeys and Keyboards doesn't fit
Key: ZEPPELIN-778
URL: https://issues.apache.org/jira/browse/ZEPPELIN-778
Project: Zeppelin
Issue Type: Bug
There is a community consensus against this PR, which has not been around in
its current form for a fraction of the time that would be necessary to evaluate
it.
> On Mar 30, 2016, at 10:42 AM, Leemoonsoo wrote:
>
> Github user Leemoonsoo commented on the pull request:
>
>
> https://github
Moon - no-one has supported your view. The community in fact has
overwhelmingly rejected it. Nobody prefers 702. Nobody agrees with you.
You are simply personally obstructing this, because of your personal animosity
-- and you have been for months.
It's time for you to step out of this ---
DuyHai - the reason we've had CI issues is that CI fails to produce a sane
spark environment. What's happening with this class is that for some versions
of spark and not others, spark fails to start. While the class has been around
since last year it was substantially modified several times in t
Github user Leemoonsoo commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/751#issuecomment-203467586
Thanks for taking care of virtual machine script.
Looks good to me.
---
If your project is set up for it, you can reply to this email and have yo
Github user Leemoonsoo commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/702#issuecomment-203465720
Appreciate @echarles for the R interpreter implementation and very open
communication.
And thanks @jeffsteinmetz for providing great review and verific
Amos,
Please get familiarize with yourself more about contribution and review
process.
https://github.com/apache/incubator-zeppelin/blob/master/CONTRIBUTING.md#the-review-process
It's not ready while PPMC really made no +1 vote for 208 for last couple of
months while it's breaking CI.
Consensus
Hi Amos,
It's good to see you working hard to making CI green.
Seems last commit of 208 [1] completely removes ZeppelinSparkClusterTest.
I don't think that is proper way to make CI green.
Amos, could you bring those test back and see if 208 pass the test?
Thanks,
moon
[1]
https://github.com/ap
Thanks Moon,
I've dropped Ignite support and PR-760 is passing CI.
Trevor Grant
Data Scientist
https://github.com/rawkintrevo
http://stackexchange.com/users/3002022/rawkintrevo
http://trevorgrant.org
*"Fortunate is he, who is able to know the causes of things." -Virgil*
On Wed, Mar 30, 2016 a
Trevor Grant created ZEPPELIN-777:
-
Summary: Add math formula support for Markdown interpretter
Key: ZEPPELIN-777
URL: https://issues.apache.org/jira/browse/ZEPPELIN-777
Project: Zeppelin
Iss
Thanks Moon.
Moving forward on this now.
Trevor Grant
Data Scientist
https://github.com/rawkintrevo
http://stackexchange.com/users/3002022/rawkintrevo
http://trevorgrant.org
*"Fortunate is he, who is able to know the causes of things." -Virgil*
On Wed, Mar 30, 2016 at 1:16 AM, moon soo Lee
Github user r-kamath closed the pull request at:
https://github.com/apache/incubator-zeppelin/pull/805
---
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
So IF the community has decided to *remove* a test to merge in #208, I'm
fine with it.
Sorry if I get angry quickly. I still have a weird feeling about this
process:
1. remove a test to make CI green
2. merge the PR
3. fix the culprit test (if it's really the cause of CI being broken)
Until now,
@doanduyhai this is definitely not a fraud and we should be careful before
writing something like this in the mail thread.
The *Temporary * removal of this test is discussed on the thread (this on
or another) and the fact the CI is green is a good progress.
Since it *seams* as if this class has no
Wait a minute!
I withdraw my vote for the merge.
After throwing a carefully look at Amos last commit, it looks like a
fraud...
He just removed completely an existing test class :
https://github.com/apache/incubator-zeppelin/pull/208/commits/14951feb6fd6cfaa2ab3fd9aa6bdbb4c04117724
Amos, do you
+1 to merge without delaying it further.
Thanks,
Sam.
On Wed, Mar 30, 2016 at 1:01 PM, DuyHai Doan wrote:
> I have just thrown an eye on PR208 and indeed it passes green so I don't
> see any reason to delay the merge.
>
> Hopefully we can close soon this poisoning debate that lasts too long
> a
I have just thrown an eye on PR208 and indeed it passes green so I don't
see any reason to delay the merge.
Hopefully we can close soon this poisoning debate that lasts too long
already
Le 30 mars 2016 07:33, "Amos Elberg" a écrit :
> Alex - there are no technical things blocking 208.
>
> You po
Github user echarles commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/702#issuecomment-203283238
@jeffsteinmetz thx, just pushed a change to show the unlist example.
---
If your project is set up for it, you can reply to this email and have your
reply a
53 matches
Mail list logo
