Github user Leemoonsoo commented on the issue:
https://github.com/apache/zeppelin/pull/747
@bzz Sure
---
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
Github user bzz commented on the issue:
https://github.com/apache/zeppelin/pull/747
@Leemoonsoo could you into non-trivial merge conflicts that happen on
merging to `branch-0.6` ?
---
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 issue:
https://github.com/apache/zeppelin/pull/747
Merging it into master and branch-0.6
---
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
e
Github user bzz commented on the issue:
https://github.com/apache/zeppelin/pull/747
Looks great to me! Thank you @lresende
Let's merge if there is no further discussion
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user Leemoonsoo commented on the issue:
https://github.com/apache/zeppelin/pull/747
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 have this feature
enabled and wishes so
Github user lresende commented on the issue:
https://github.com/apache/zeppelin/pull/747
@Leemoonsoo all back to green
---
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
Github user Leemoonsoo commented on the issue:
https://github.com/apache/zeppelin/pull/747
Looks like there were some network problem on last CI bulid. Could you
trigger ci once again and see if it goes to green?
---
If your project is set up for it, you can reply to this email and h
Github user lresende commented on the issue:
https://github.com/apache/zeppelin/pull/747
@bzz and @Leemoonsoo
I have updated the readme to match the ci, and also refactored the
reflection utility methods to a separate class.
---
If your project is set up for it, you can rep
Github user bzz commented on the issue:
https://github.com/apache/zeppelin/pull/747
Looks ð ð¯ 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 have this feature
enabled and wishe
Github user Leemoonsoo commented on the issue:
https://github.com/apache/zeppelin/pull/747
@lresende Awesome!
Tested and 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 lresende commented on the issue:
https://github.com/apache/zeppelin/pull/747
@Leemoonsoo All green again.
---
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
Github user Leemoonsoo commented on the issue:
https://github.com/apache/zeppelin/pull/747
@lresende Could you trigger CI again and see if scala-2.11 profile pass the
flaky test?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user lresende commented on the issue:
https://github.com/apache/zeppelin/pull/747
We finally got a green build with Scala 2.11 thanks for @Leemoonsoo help on
resolving the couple remaining issues... I now also rebased to latest master
and this PR should be ready to final review
13 matches
Mail list logo
