Github user anthonycorbacho commented on the issue:
https://github.com/apache/zeppelin/pull/2161
Tested with some basic case, look 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
Github user AhyoungRyu commented on the issue:
https://github.com/apache/zeppelin/pull/2161
I tested two scenarios that you described and both(turn on & off Shiro) are
working well.
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user khalidhuseynov commented on the issue:
https://github.com/apache/zeppelin/pull/2161
@anthonycorbacho thanks for the feedback, addressed them above. Let me know
if there's something else and if it works fine for you.
Also would be nice if other members could
Github user khalidhuseynov commented on the issue:
https://github.com/apache/zeppelin/pull/2161
/cc @anthonycorbacho @Leemoonsoo @AhyoungRyu plz help to review and test
this one
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user khalidhuseynov commented on the issue:
https://github.com/apache/zeppelin/pull/2161
yes, i think my fork was integrated with travis since i have the build here
https://travis-ci.org/khalidhuseynov/incubator-zeppelin/builds/212981024 . also
the branch was rebased today and
Github user Leemoonsoo commented on the issue:
https://github.com/apache/zeppelin/pull/2161
Current jenkins script check only
https://travis-ci.org/khalidhuseynov/zeppelin/ not
https://travis-ci.org/khalidhuseynov/incubator-zeppelin/. Could you setup
travis with 'zeppelin'
Github user Leemoonsoo commented on the issue:
https://github.com/apache/zeppelin/pull/2161
Can you setup
[CI](http://zeppelin.apache.org/contribution/contributions.html#continuous-integration)
for you fork?
And then you'll need rebase this branch to include some fixes for
