Can this be fixed by adding a default configuration someplace? Might be an
easy fix
On Sun, Jun 19, 2016 at 10:46 PM, Hyung Sung Shim <hss...@nflabs.com> wrote:
> Great point @Corneau Damien.
> I got an following error when i control the paragraph.
>
> ERROR [2016-06-20 11:41:02,473] ({qtp1424826835-36}
> NotebookServer.java[onMessage]:232) - Can't handle message
> org.apache.shiro.UnavailableSecurityManagerException: No SecurityManager
> accessible to the calling code, either bound to the
> org.apache.shiro.util.ThreadContext or as a vm static singleton. This is
> an invalid application configuration.
> at
> org.apache.shiro.SecurityUtils.getSecurityManager(SecurityUtils.java:123)
> at org.apache.shiro.subject.Subject$Builder.<init>(Subject.java:627)
> at org.apache.shiro.SecurityUtils.getSubject(SecurityUtils.java:56)
> at
> org.apache.zeppelin.utils.SecurityUtils.getPrincipal(SecurityUtils.java:60)
> at
> org.apache.zeppelin.socket.NotebookServer.removeParagraph(NotebookServer.java:684)
> at
> org.apache.zeppelin.socket.NotebookServer.onMessage(NotebookServer.java:194)
> at
> org.apache.zeppelin.socket.NotebookSocket.onWebSocketText(NotebookSocket.java:56)
> at
> org.eclipse.jetty.websocket.common.events.JettyListenerEventDriver.onTextMessage(JettyListenerEventDriver.java:128)
> at
> org.eclipse.jetty.websocket.common.message.SimpleTextMessage.messageComplete(SimpleTextMessage.java:69)
> at
> org.eclipse.jetty.websocket.common.events.AbstractEventDriver.appendMessage(AbstractEventDriver.java:65)
> at
> org.eclipse.jetty.websocket.common.events.JettyListenerEventDriver.onTextFrame(JettyListenerEventDriver.java:122)
> at
> org.eclipse.jetty.websocket.common.events.AbstractEventDriver.incomingFrame(AbstractEventDriver.java:161)
> at
> org.eclipse.jetty.websocket.common.WebSocketSession.incomingFrame(WebSocketSession.java:309)
> at
> org.eclipse.jetty.websocket.common.extensions.ExtensionStack.incomingFrame(ExtensionStack.java:214)
> at org.eclipse.jetty.websocket.common.Parser.notifyFrame(Parser.java:220)
> at org.eclipse.jetty.websocket.common.Parser.parse(Parser.java:258)
> at
> org.eclipse.jetty.websocket.common.io.AbstractWebSocketConnection.readParse(AbstractWebSocketConnection.java:632)
> at
> org.eclipse.jetty.websocket.common.io.AbstractWebSocketConnection.onFillable(AbstractWebSocketConnection.java:480)
> at
> org.eclipse.jetty.io.AbstractConnection$2.run(AbstractConnection.java:544)
> at
> org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:635)
> at
> org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:555)
> at java.lang.Thread.run(Thread.java:745)
>
>
>
>
> 2016-06-20 11:40 GMT+09:00 Corneau Damien <cornead...@gmail.com>:
>
>> The culprit is this commit:
>>
>> https://github.com/apache/zeppelin/commit/4a0dce525304ddee8a69bffc3eee20f4bbf4f209
>>
>> On Mon, Jun 20, 2016 at 11:33 AM, Hyung Sung Shim <hss...@nflabs.com>
>> wrote:
>>
>>> Hi.
>>> I'll take care of this issue. give me a minute.
>>>
>>> 2016-06-20 9:14 GMT+09:00 Randy Gelhausen <rgel...@gmail.com>:
>>>
>>>> Anyone else seeing this issue and/or know how to resolve it?
>>>>
>>>> I've deleted and re-cloned/rebuilt the entire project (and my maven
>>>> cache), restarted Chrome and my machine, but no luck.
>>>>
>>>> Still can't re-order or remove paragraphs from current master.
>>>>
>>>> On Sun, Jun 19, 2016 at 2:30 PM, Randy Gelhausen <rgel...@gmail.com>
>>>> wrote:
>>>>
>>>>> Filed: https://issues.apache.org/jira/browse/ZEPPELIN-1033
>>>>>
>>>>> On Sun, Jun 19, 2016 at 1:36 PM, moon soo Lee <m...@apache.org> wrote:
>>>>>
>>>>>> Thanks for sharing the problem.
>>>>>> Can't see attached gif, in this mailing list.
>>>>>>
>>>>>> Do you mind create an jira issue?
>>>>>>
>>>>>> Thanks,
>>>>>> moon
>>>>>>
>>>>>>
>>>>>> On Sat, Jun 18, 2016 at 10:06 PM Randy Gelhausen <rgel...@gmail.com>
>>>>>> wrote:
>>>>>>
>>>>>> > I just rebuilt from master and found that in both Firefox and
>>>>>> Chrome, I
>>>>>> > can no longer remove paragraphs or re-order them via the gear icon
>>>>>> next to
>>>>>> > each paragraph.
>>>>>> >
>>>>>> > See the attached gif for an example.
>>>>>> >
>>>>>> > Did a recent merge break this functionality?
>>>>>> >
>>>>>>
>>>>>
>>>>>
>>>>
>>>
>>
>
