Github user corneadoug commented on the issue:
https://github.com/apache/incubator-zeppelin/pull/904
@mwkang It's fine, we can always reopen it if necessary. Just wanted
@Leemoonsoo go to close it since he was the one to report it
---
If your project is set up for it, you can reply
Github user mwkang commented on the issue:
https://github.com/apache/incubator-zeppelin/pull/904
Oh.. I closed JIRA issue.
I am so sorry that I act at my discretion.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If
Github user corneadoug commented on the issue:
https://github.com/apache/incubator-zeppelin/pull/904
@Leemoonsoo Can we close this JIRA issue then?
https://issues.apache.org/jira/browse/ZEPPELIN-835
---
If your project is set up for it, you can reply to this email and have your
Github user mwkang commented on the issue:
https://github.com/apache/incubator-zeppelin/pull/904
Related PR: https://github.com/apache/incubator-zeppelin/pull/860
Related Issue: https://issues.apache.org/jira/browse/ZEPPELIN-828
---
If your project is set up for it, you can reply
Github user mwkang commented on the issue:
https://github.com/apache/incubator-zeppelin/pull/904
While I rebase this PR, I found this issue was been resolved
[AuthenticationInfo in master].
So I closed PR.
[AuthenticationInfo in master]:
Github user corneadoug commented on the issue:
https://github.com/apache/incubator-zeppelin/pull/904
@mwkang Could you rebase this PR please?
---
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
