[jira] [Assigned] (UIMA-6204) createReaderDescription does not discover type priorities
[
https://issues.apache.org/jira/browse/UIMA-6204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Eckart de Castilho reassigned UIMA-6204:
Assignee: Richard Eckart de Castilho
> createReaderDescription does not discover type priorities
> -
>
> Key: UIMA-6204
> URL: https://issues.apache.org/jira/browse/UIMA-6204
> Project: UIMA
> Issue Type: Bug
> Components: uimaFIT
>Affects Versions: 2.4.0uimaFIT
>Reporter: Richard Eckart de Castilho
>Assignee: Richard Eckart de Castilho
>Priority: Major
> Fix For: 2.5.0uimaFIT
>
>
> createReaderDescription does not discover type priorities. This may cause the
> JCas to be incompletely initialised (i.e. without type priorities), e.g. when
> only such a reader is used in a JCasIterable. A workaround is to add a No-op
> analysis engine to the JCasIterable:
> {code}
> JCasIterable pipeline = SimplePipeline.iteratePipeline(readerDescription,
> createEngineDescription(NoOpAnnotator.class));
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (UIMA-6204) createReaderDescription does not discover type priorities
Richard Eckart de Castilho created UIMA-6204:
Summary: createReaderDescription does not discover type priorities
Key: UIMA-6204
URL: https://issues.apache.org/jira/browse/UIMA-6204
Project: UIMA
Issue Type: Bug
Components: uimaFIT
Affects Versions: 2.4.0uimaFIT
Reporter: Richard Eckart de Castilho
Fix For: 2.5.0uimaFIT
createReaderDescription does not discover type priorities. This may cause the
JCas to be incompletely initialised (i.e. without type priorities), e.g. when
only such a reader is used in a JCasIterable. A workaround is to add a No-op
analysis engine to the JCasIterable:
{code}
JCasIterable pipeline = SimplePipeline.iteratePipeline(readerDescription,
createEngineDescription(NoOpAnnotator.class));
{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Work stopped] (UIMA-6193) Ruta: Initial assignment of list variables behaves strangely
[
https://issues.apache.org/jira/browse/UIMA-6193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on UIMA-6193 stopped by Peter Klügl.
-
> Ruta: Initial assignment of list variables behaves strangely
>
>
> Key: UIMA-6193
> URL: https://issues.apache.org/jira/browse/UIMA-6193
> Project: UIMA
> Issue Type: Bug
> Components: Ruta
>Affects Versions: 2.8.0ruta
>Reporter: Michael Stenger
>Assignee: Peter Klügl
>Priority: Minor
> Fix For: 2.8.1ruta, 3.0.1ruta
>
>
> When list variables are declared with a list containing variables as initial
> value, the managing VariableListExpression seems to save the variable
> expression given with that argument list instead of the represented values.
> E.g.
> {code:java}
> INTLIST somelist = {var};{code}
> for a variable
> {code:java}
> INT var = 1;
> {code}
> stores the expression behind var instead of the value 1. So changing the
> value of var after the declaration of somelist still effects the value of
> somelist[0]. That's not the case if ADD was used instead.
> Consider this example:
> {code:java}
> DECLARE testType (StringArray arr);
> STRING s = "a";
> STRINGLIST sl = {s};
> Document{ -> ADD(sl, s), s = "b", CREATE(testType, "arr" = sl)};{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Work started] (UIMA-6193) Ruta: Initial assignment of list variables behaves strangely
[
https://issues.apache.org/jira/browse/UIMA-6193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on UIMA-6193 started by Peter Klügl.
-
> Ruta: Initial assignment of list variables behaves strangely
>
>
> Key: UIMA-6193
> URL: https://issues.apache.org/jira/browse/UIMA-6193
> Project: UIMA
> Issue Type: Bug
> Components: Ruta
>Affects Versions: 2.8.0ruta
>Reporter: Michael Stenger
>Assignee: Peter Klügl
>Priority: Minor
> Fix For: 2.8.1ruta, 3.0.1ruta
>
>
> When list variables are declared with a list containing variables as initial
> value, the managing VariableListExpression seems to save the variable
> expression given with that argument list instead of the represented values.
> E.g.
> {code:java}
> INTLIST somelist = {var};{code}
> for a variable
> {code:java}
> INT var = 1;
> {code}
> stores the expression behind var instead of the value 1. So changing the
> value of var after the declaration of somelist still effects the value of
> somelist[0]. That's not the case if ADD was used instead.
> Consider this example:
> {code:java}
> DECLARE testType (StringArray arr);
> STRING s = "a";
> STRINGLIST sl = {s};
> Document{ -> ADD(sl, s), s = "b", CREATE(testType, "arr" = sl)};{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (UIMA-6194) Ruta: RutaLiteralMatcher throws exception for special choice of string
[
https://issues.apache.org/jira/browse/UIMA-6194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Peter Klügl resolved UIMA-6194.
---
Resolution: Fixed
> Ruta: RutaLiteralMatcher throws exception for special choice of string
> --
>
> Key: UIMA-6194
> URL: https://issues.apache.org/jira/browse/UIMA-6194
> Project: UIMA
> Issue Type: Bug
> Components: Ruta
>Affects Versions: 2.8.0ruta
>Reporter: Michael Stenger
>Assignee: Peter Klügl
>Priority: Minor
> Fix For: 2.8.1ruta, 3.0.1ruta
>
>
> For certain combinations of document text and RuleElementLiteral in the
> script, method getAnnotation of class RutaLiteralMatcher throws a
> NullPointerException. This seems to be the case whenever the used string is
> a postfix or infix of a word in the document, but itself doesn't occur.
> h4. Example
> Script
>
> {code:java}
> DECLARE testType;
> "est" {-> testType};
> "est te"{-> testType};
> {code}
> Document
>
> {code:java}
> test test{code}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (UIMA-6195) RutaLiteralMatcher throws NPE
[
https://issues.apache.org/jira/browse/UIMA-6195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Peter Klügl resolved UIMA-6195.
---
Resolution: Fixed
> RutaLiteralMatcher throws NPE
> --
>
> Key: UIMA-6195
> URL: https://issues.apache.org/jira/browse/UIMA-6195
> Project: UIMA
> Issue Type: Bug
> Components: Ruta
>Affects Versions: 3.0.0ruta
>Reporter: Dominic Jehle
>Assignee: Peter Klügl
>Priority: Critical
> Fix For: 3.0.1ruta
>
> Attachments: 1_Debug_View.JPG, 2_Debug_View_Types.JPG
>
>
> *Problem*
> During update to ruta 3.0.0. from 2.6.1, one of my rules started to throw an
> NPE at execution in RutaLiteralMatcher.
> *Example*
> It's a very simple rule with a literal upper case "I" followed by a previous
> match (in this case underscores):
> {code:java}
> "+" -> SIMPLEFORMATTING;
> "I" SIMPLEFORMATTING "I"? { -> MARKONCE(FORMATTING,1,2)};
> {code}
> When run on input like
> {code:java}
> "PI_I How to test it?"{code}
> it crashes with NPE. Input like
> {code:java}
> "P I_I How to test it?"{code}
> is fine.
> Here's the stack:
> {code:java}
> org.apache.uima.analysis_engine.AnalysisEngineProcessException: Annotator
> processing failed.
> org.apache.uima.analysis_engine.AnalysisEngineProcessException: Annotator
> processing failed. at
> org.apache.uima.ruta.engine.RutaEngine.process(RutaEngine.java:614) at
> org.apache.uima.analysis_component.JCasAnnotator_ImplBase.process(JCasAnnotator_ImplBase.java:48)
> at
> org.apache.uima.analysis_engine.impl.AnalysisEngineImplBase.lambda$callProcessMethod$3(AnalysisEngineImplBase.java:626)
> at
> org.apache.uima.analysis_engine.impl.AnalysisEngineImplBase.withContexts(AnalysisEngineImplBase.java:653)
> at
> org.apache.uima.analysis_engine.impl.AnalysisEngineImplBase.callProcessMethod(AnalysisEngineImplBase.java:623)
> at
> org.apache.uima.analysis_engine.impl.PrimitiveAnalysisEngine_impl.callAnalysisComponentProcess(PrimitiveAnalysisEngine_impl.java:381)
> at
> org.apache.uima.analysis_engine.impl.PrimitiveAnalysisEngine_impl.processAndOutputNewCASes(PrimitiveAnalysisEngine_impl.java:299)
> at
> org.apache.uima.analysis_engine.impl.AnalysisEngineImplBase.process(AnalysisEngineImplBase.java:272)
> at
> org.apache.uima.analysis_engine.impl.AnalysisEngineImplBase.process(AnalysisEngineImplBase.java:287)
> at
> com.myorg.uima.ruta.recognizer.RecognizerFormattingFactoryTest.run(RecognizerFormattingFactoryTest.java:208)
> at
> com.myorg.uima.ruta.recognizer.RecognizerFormattingFactoryTest.testFormattingRutaUpdateBug2020(RecognizerFormattingFactoryTest.java:191)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498) at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325) at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290) at
> org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71) at
> org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288) at
> org.junit.runners.ParentRunner.access$000(ParentRunner.java:58) at
> org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268) at
> org.junit.runners.ParentRunner.run(ParentRunner.java:363) at
> org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:89)
> at
> org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:41)
> at
> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:541)
> at
> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:763)
> at
> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:463)
> at
> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:209)Caused
> by: java.lang.NullPointerException at
> org.apache.uima.ruta.rule.RutaLiteralMatcher.getAnnotation(RutaLiteralMatcher.java:72)
> at
> org.apache.uima.ruta.rule.RutaLiteralMatcher.getMatchingAnnotations(RutaLiteralMatcher.java:62)
> at
> org.apache.uima.ruta.rule.RutaLiteralMatche
[jira] [Commented] (UIMA-6203) Add SerialFormat.XMI_PRETTY
[ https://issues.apache.org/jira/browse/UIMA-6203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17063534#comment-17063534 ] Peter Klügl commented on UIMA-6203: --- Oh this would be great! > Add SerialFormat.XMI_PRETTY > --- > > Key: UIMA-6203 > URL: https://issues.apache.org/jira/browse/UIMA-6203 > Project: UIMA > Issue Type: New Feature > Components: Core Java Framework >Reporter: Richard Eckart de Castilho >Priority: Major > > It would be nice to have a SerialFormat.XMI_PRETTY which pretty-prints the > written XMI. The SerialFormat.XMI writes everything into a single line which > is quite unreadable with the human eye. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (UIMA-6203) Add SerialFormat.XMI_PRETTY
Richard Eckart de Castilho created UIMA-6203: Summary: Add SerialFormat.XMI_PRETTY Key: UIMA-6203 URL: https://issues.apache.org/jira/browse/UIMA-6203 Project: UIMA Issue Type: New Feature Components: Core Java Framework Reporter: Richard Eckart de Castilho It would be nice to have a SerialFormat.XMI_PRETTY which pretty-prints the written XMI. The SerialFormat.XMI writes everything into a single line which is quite unreadable with the human eye. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (UIMA-6194) Ruta: RutaLiteralMatcher throws exception for special choice of string
[
https://issues.apache.org/jira/browse/UIMA-6194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17063367#comment-17063367
]
Peter Klügl commented on UIMA-6194:
---
Hi, sorry for the delayed response. This should already been fixed in the
current trunk/snapshot. I will prepare a bugfix release asap.
> Ruta: RutaLiteralMatcher throws exception for special choice of string
> --
>
> Key: UIMA-6194
> URL: https://issues.apache.org/jira/browse/UIMA-6194
> Project: UIMA
> Issue Type: Bug
> Components: Ruta
>Affects Versions: 2.8.0ruta
>Reporter: Michael Stenger
>Assignee: Peter Klügl
>Priority: Minor
> Fix For: 2.8.1ruta, 3.0.1ruta
>
>
> For certain combinations of document text and RuleElementLiteral in the
> script, method getAnnotation of class RutaLiteralMatcher throws a
> NullPointerException. This seems to be the case whenever the used string is
> a postfix or infix of a word in the document, but itself doesn't occur.
> h4. Example
> Script
>
> {code:java}
> DECLARE testType;
> "est" {-> testType};
> "est te"{-> testType};
> {code}
> Document
>
> {code:java}
> test test{code}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (UIMA-6195) RutaLiteralMatcher throws NPE
[
https://issues.apache.org/jira/browse/UIMA-6195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17063365#comment-17063365
]
Peter Klügl commented on UIMA-6195:
---
Yes, the problem is gone in the current trunk.
> RutaLiteralMatcher throws NPE
> --
>
> Key: UIMA-6195
> URL: https://issues.apache.org/jira/browse/UIMA-6195
> Project: UIMA
> Issue Type: Bug
> Components: Ruta
>Affects Versions: 3.0.0ruta
>Reporter: Dominic Jehle
>Assignee: Peter Klügl
>Priority: Critical
> Fix For: 3.0.1ruta
>
> Attachments: 1_Debug_View.JPG, 2_Debug_View_Types.JPG
>
>
> *Problem*
> During update to ruta 3.0.0. from 2.6.1, one of my rules started to throw an
> NPE at execution in RutaLiteralMatcher.
> *Example*
> It's a very simple rule with a literal upper case "I" followed by a previous
> match (in this case underscores):
> {code:java}
> "+" -> SIMPLEFORMATTING;
> "I" SIMPLEFORMATTING "I"? { -> MARKONCE(FORMATTING,1,2)};
> {code}
> When run on input like
> {code:java}
> "PI_I How to test it?"{code}
> it crashes with NPE. Input like
> {code:java}
> "P I_I How to test it?"{code}
> is fine.
> Here's the stack:
> {code:java}
> org.apache.uima.analysis_engine.AnalysisEngineProcessException: Annotator
> processing failed.
> org.apache.uima.analysis_engine.AnalysisEngineProcessException: Annotator
> processing failed. at
> org.apache.uima.ruta.engine.RutaEngine.process(RutaEngine.java:614) at
> org.apache.uima.analysis_component.JCasAnnotator_ImplBase.process(JCasAnnotator_ImplBase.java:48)
> at
> org.apache.uima.analysis_engine.impl.AnalysisEngineImplBase.lambda$callProcessMethod$3(AnalysisEngineImplBase.java:626)
> at
> org.apache.uima.analysis_engine.impl.AnalysisEngineImplBase.withContexts(AnalysisEngineImplBase.java:653)
> at
> org.apache.uima.analysis_engine.impl.AnalysisEngineImplBase.callProcessMethod(AnalysisEngineImplBase.java:623)
> at
> org.apache.uima.analysis_engine.impl.PrimitiveAnalysisEngine_impl.callAnalysisComponentProcess(PrimitiveAnalysisEngine_impl.java:381)
> at
> org.apache.uima.analysis_engine.impl.PrimitiveAnalysisEngine_impl.processAndOutputNewCASes(PrimitiveAnalysisEngine_impl.java:299)
> at
> org.apache.uima.analysis_engine.impl.AnalysisEngineImplBase.process(AnalysisEngineImplBase.java:272)
> at
> org.apache.uima.analysis_engine.impl.AnalysisEngineImplBase.process(AnalysisEngineImplBase.java:287)
> at
> com.myorg.uima.ruta.recognizer.RecognizerFormattingFactoryTest.run(RecognizerFormattingFactoryTest.java:208)
> at
> com.myorg.uima.ruta.recognizer.RecognizerFormattingFactoryTest.testFormattingRutaUpdateBug2020(RecognizerFormattingFactoryTest.java:191)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498) at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325) at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290) at
> org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71) at
> org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288) at
> org.junit.runners.ParentRunner.access$000(ParentRunner.java:58) at
> org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268) at
> org.junit.runners.ParentRunner.run(ParentRunner.java:363) at
> org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:89)
> at
> org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:41)
> at
> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:541)
> at
> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:763)
> at
> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:463)
> at
> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:209)Caused
> by: java.lang.NullPointerException at
> org.apache.uima.ruta.rule.RutaLiteralMatcher.getAnnotation(RutaLiteralMatcher.java:72)
> at
> org.apache.uima.ruta.rule.RutaLiteralMatcher.getMatchingAnnotations
[jira] [Created] (UIMA-6202) updates due to ASF change for distribution of software
Marshall Schor created UIMA-6202: Summary: updates due to ASF change for distribution of software Key: UIMA-6202 URL: https://issues.apache.org/jira/browse/UIMA-6202 Project: UIMA Issue Type: Task Reporter: Marshall Schor ASF Infra changed how artifacts are being distributed, and asks we update our websites/documentation/anything-else that referes to apache/dist (which is being deprecated). Here's a link to what's happening: [https://blogs.apache.org/infra/entry/more-secure-and-robust-downloads] I'll scan our website docs and fix things there. Other projects may have references to dist in their build processes that may need updating. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Work started] (UIMA-6195) RutaLiteralMatcher throws NPE
[
https://issues.apache.org/jira/browse/UIMA-6195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on UIMA-6195 started by Peter Klügl.
-
> RutaLiteralMatcher throws NPE
> --
>
> Key: UIMA-6195
> URL: https://issues.apache.org/jira/browse/UIMA-6195
> Project: UIMA
> Issue Type: Bug
> Components: Ruta
>Affects Versions: 3.0.0ruta
>Reporter: Dominic Jehle
>Assignee: Peter Klügl
>Priority: Critical
> Attachments: 1_Debug_View.JPG, 2_Debug_View_Types.JPG
>
>
> *Problem*
> During update to ruta 3.0.0. from 2.6.1, one of my rules started to throw an
> NPE at execution in RutaLiteralMatcher.
> *Example*
> It's a very simple rule with a literal upper case "I" followed by a previous
> match (in this case underscores):
> {code:java}
> "+" -> SIMPLEFORMATTING;
> "I" SIMPLEFORMATTING "I"? { -> MARKONCE(FORMATTING,1,2)};
> {code}
> When run on input like
> {code:java}
> "PI_I How to test it?"{code}
> it crashes with NPE. Input like
> {code:java}
> "P I_I How to test it?"{code}
> is fine.
> Here's the stack:
> {code:java}
> org.apache.uima.analysis_engine.AnalysisEngineProcessException: Annotator
> processing failed.
> org.apache.uima.analysis_engine.AnalysisEngineProcessException: Annotator
> processing failed. at
> org.apache.uima.ruta.engine.RutaEngine.process(RutaEngine.java:614) at
> org.apache.uima.analysis_component.JCasAnnotator_ImplBase.process(JCasAnnotator_ImplBase.java:48)
> at
> org.apache.uima.analysis_engine.impl.AnalysisEngineImplBase.lambda$callProcessMethod$3(AnalysisEngineImplBase.java:626)
> at
> org.apache.uima.analysis_engine.impl.AnalysisEngineImplBase.withContexts(AnalysisEngineImplBase.java:653)
> at
> org.apache.uima.analysis_engine.impl.AnalysisEngineImplBase.callProcessMethod(AnalysisEngineImplBase.java:623)
> at
> org.apache.uima.analysis_engine.impl.PrimitiveAnalysisEngine_impl.callAnalysisComponentProcess(PrimitiveAnalysisEngine_impl.java:381)
> at
> org.apache.uima.analysis_engine.impl.PrimitiveAnalysisEngine_impl.processAndOutputNewCASes(PrimitiveAnalysisEngine_impl.java:299)
> at
> org.apache.uima.analysis_engine.impl.AnalysisEngineImplBase.process(AnalysisEngineImplBase.java:272)
> at
> org.apache.uima.analysis_engine.impl.AnalysisEngineImplBase.process(AnalysisEngineImplBase.java:287)
> at
> com.myorg.uima.ruta.recognizer.RecognizerFormattingFactoryTest.run(RecognizerFormattingFactoryTest.java:208)
> at
> com.myorg.uima.ruta.recognizer.RecognizerFormattingFactoryTest.testFormattingRutaUpdateBug2020(RecognizerFormattingFactoryTest.java:191)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498) at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325) at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290) at
> org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71) at
> org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288) at
> org.junit.runners.ParentRunner.access$000(ParentRunner.java:58) at
> org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268) at
> org.junit.runners.ParentRunner.run(ParentRunner.java:363) at
> org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:89)
> at
> org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:41)
> at
> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:541)
> at
> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:763)
> at
> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:463)
> at
> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:209)Caused
> by: java.lang.NullPointerException at
> org.apache.uima.ruta.rule.RutaLiteralMatcher.getAnnotation(RutaLiteralMatcher.java:72)
> at
> org.apache.uima.ruta.rule.RutaLiteralMatcher.getMatchingAnnotations(RutaLiteralMatcher.java:62)
> at
> org.apache.uima.ruta.rule.RutaLiteralMatcher.getMatchingAnnotations(RutaLiteralMa
[jira] [Updated] (UIMA-6195) RutaLiteralMatcher throws NPE
[
https://issues.apache.org/jira/browse/UIMA-6195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Peter Klügl updated UIMA-6195:
--
Fix Version/s: 3.0.1ruta
> RutaLiteralMatcher throws NPE
> --
>
> Key: UIMA-6195
> URL: https://issues.apache.org/jira/browse/UIMA-6195
> Project: UIMA
> Issue Type: Bug
> Components: Ruta
>Affects Versions: 3.0.0ruta
>Reporter: Dominic Jehle
>Assignee: Peter Klügl
>Priority: Critical
> Fix For: 3.0.1ruta
>
> Attachments: 1_Debug_View.JPG, 2_Debug_View_Types.JPG
>
>
> *Problem*
> During update to ruta 3.0.0. from 2.6.1, one of my rules started to throw an
> NPE at execution in RutaLiteralMatcher.
> *Example*
> It's a very simple rule with a literal upper case "I" followed by a previous
> match (in this case underscores):
> {code:java}
> "+" -> SIMPLEFORMATTING;
> "I" SIMPLEFORMATTING "I"? { -> MARKONCE(FORMATTING,1,2)};
> {code}
> When run on input like
> {code:java}
> "PI_I How to test it?"{code}
> it crashes with NPE. Input like
> {code:java}
> "P I_I How to test it?"{code}
> is fine.
> Here's the stack:
> {code:java}
> org.apache.uima.analysis_engine.AnalysisEngineProcessException: Annotator
> processing failed.
> org.apache.uima.analysis_engine.AnalysisEngineProcessException: Annotator
> processing failed. at
> org.apache.uima.ruta.engine.RutaEngine.process(RutaEngine.java:614) at
> org.apache.uima.analysis_component.JCasAnnotator_ImplBase.process(JCasAnnotator_ImplBase.java:48)
> at
> org.apache.uima.analysis_engine.impl.AnalysisEngineImplBase.lambda$callProcessMethod$3(AnalysisEngineImplBase.java:626)
> at
> org.apache.uima.analysis_engine.impl.AnalysisEngineImplBase.withContexts(AnalysisEngineImplBase.java:653)
> at
> org.apache.uima.analysis_engine.impl.AnalysisEngineImplBase.callProcessMethod(AnalysisEngineImplBase.java:623)
> at
> org.apache.uima.analysis_engine.impl.PrimitiveAnalysisEngine_impl.callAnalysisComponentProcess(PrimitiveAnalysisEngine_impl.java:381)
> at
> org.apache.uima.analysis_engine.impl.PrimitiveAnalysisEngine_impl.processAndOutputNewCASes(PrimitiveAnalysisEngine_impl.java:299)
> at
> org.apache.uima.analysis_engine.impl.AnalysisEngineImplBase.process(AnalysisEngineImplBase.java:272)
> at
> org.apache.uima.analysis_engine.impl.AnalysisEngineImplBase.process(AnalysisEngineImplBase.java:287)
> at
> com.myorg.uima.ruta.recognizer.RecognizerFormattingFactoryTest.run(RecognizerFormattingFactoryTest.java:208)
> at
> com.myorg.uima.ruta.recognizer.RecognizerFormattingFactoryTest.testFormattingRutaUpdateBug2020(RecognizerFormattingFactoryTest.java:191)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498) at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325) at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290) at
> org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71) at
> org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288) at
> org.junit.runners.ParentRunner.access$000(ParentRunner.java:58) at
> org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268) at
> org.junit.runners.ParentRunner.run(ParentRunner.java:363) at
> org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:89)
> at
> org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:41)
> at
> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:541)
> at
> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:763)
> at
> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:463)
> at
> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:209)Caused
> by: java.lang.NullPointerException at
> org.apache.uima.ruta.rule.RutaLiteralMatcher.getAnnotation(RutaLiteralMatcher.java:72)
> at
> org.apache.uima.ruta.rule.RutaLiteralMatcher.getMatchingAnnotations(RutaLiteralMatcher.java:62)
> at
> org.apache.uima.ruta.rule.RutaLiteralM
[jira] [Commented] (UIMA-6195) RutaLiteralMatcher throws NPE
[
https://issues.apache.org/jira/browse/UIMA-6195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17063362#comment-17063362
]
Peter Klügl commented on UIMA-6195:
---
Yes, this is most likely already fixed in the current trunk/snapshot. I will
add a test and reproduce it just to be sure. Then, I will prepare a bugfix
release, but no promises when exactly (in these corona times).
> RutaLiteralMatcher throws NPE
> --
>
> Key: UIMA-6195
> URL: https://issues.apache.org/jira/browse/UIMA-6195
> Project: UIMA
> Issue Type: Bug
> Components: Ruta
>Affects Versions: 3.0.0ruta
>Reporter: Dominic Jehle
>Assignee: Peter Klügl
>Priority: Critical
> Attachments: 1_Debug_View.JPG, 2_Debug_View_Types.JPG
>
>
> *Problem*
> During update to ruta 3.0.0. from 2.6.1, one of my rules started to throw an
> NPE at execution in RutaLiteralMatcher.
> *Example*
> It's a very simple rule with a literal upper case "I" followed by a previous
> match (in this case underscores):
> {code:java}
> "+" -> SIMPLEFORMATTING;
> "I" SIMPLEFORMATTING "I"? { -> MARKONCE(FORMATTING,1,2)};
> {code}
> When run on input like
> {code:java}
> "PI_I How to test it?"{code}
> it crashes with NPE. Input like
> {code:java}
> "P I_I How to test it?"{code}
> is fine.
> Here's the stack:
> {code:java}
> org.apache.uima.analysis_engine.AnalysisEngineProcessException: Annotator
> processing failed.
> org.apache.uima.analysis_engine.AnalysisEngineProcessException: Annotator
> processing failed. at
> org.apache.uima.ruta.engine.RutaEngine.process(RutaEngine.java:614) at
> org.apache.uima.analysis_component.JCasAnnotator_ImplBase.process(JCasAnnotator_ImplBase.java:48)
> at
> org.apache.uima.analysis_engine.impl.AnalysisEngineImplBase.lambda$callProcessMethod$3(AnalysisEngineImplBase.java:626)
> at
> org.apache.uima.analysis_engine.impl.AnalysisEngineImplBase.withContexts(AnalysisEngineImplBase.java:653)
> at
> org.apache.uima.analysis_engine.impl.AnalysisEngineImplBase.callProcessMethod(AnalysisEngineImplBase.java:623)
> at
> org.apache.uima.analysis_engine.impl.PrimitiveAnalysisEngine_impl.callAnalysisComponentProcess(PrimitiveAnalysisEngine_impl.java:381)
> at
> org.apache.uima.analysis_engine.impl.PrimitiveAnalysisEngine_impl.processAndOutputNewCASes(PrimitiveAnalysisEngine_impl.java:299)
> at
> org.apache.uima.analysis_engine.impl.AnalysisEngineImplBase.process(AnalysisEngineImplBase.java:272)
> at
> org.apache.uima.analysis_engine.impl.AnalysisEngineImplBase.process(AnalysisEngineImplBase.java:287)
> at
> com.myorg.uima.ruta.recognizer.RecognizerFormattingFactoryTest.run(RecognizerFormattingFactoryTest.java:208)
> at
> com.myorg.uima.ruta.recognizer.RecognizerFormattingFactoryTest.testFormattingRutaUpdateBug2020(RecognizerFormattingFactoryTest.java:191)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498) at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325) at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290) at
> org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71) at
> org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288) at
> org.junit.runners.ParentRunner.access$000(ParentRunner.java:58) at
> org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268) at
> org.junit.runners.ParentRunner.run(ParentRunner.java:363) at
> org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:89)
> at
> org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:41)
> at
> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:541)
> at
> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:763)
> at
> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:463)
> at
> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:209)Caused
> by: java.lang.NullPointerException at
> org.apache.uima.ruta.rule.Ru
[jira] [Assigned] (UIMA-6191) Ruta: Global Variable Comparison Fails
[
https://issues.apache.org/jira/browse/UIMA-6191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Peter Klügl reassigned UIMA-6191:
-
Assignee: Peter Klügl
> Ruta: Global Variable Comparison Fails
> --
>
> Key: UIMA-6191
> URL: https://issues.apache.org/jira/browse/UIMA-6191
> Project: UIMA
> Issue Type: Bug
> Components: Ruta
>Affects Versions: 2.8.0ruta
>Reporter: Viorel Morari
>Assignee: Peter Klügl
>Priority: Major
> Fix For: 2.8.1ruta, 3.0.1ruta
>
>
> Comparison of global variables in the action block of the rule fails. It
> succeeds in the condition block though.
> See {{testCompareGlobalVariableInAction}} Test in
> {{AnnotationVariableExpressionTest}}.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (UIMA-6193) Ruta: Initial assignment of list variables behaves strangely
[
https://issues.apache.org/jira/browse/UIMA-6193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Peter Klügl reassigned UIMA-6193:
-
Assignee: Peter Klügl
> Ruta: Initial assignment of list variables behaves strangely
>
>
> Key: UIMA-6193
> URL: https://issues.apache.org/jira/browse/UIMA-6193
> Project: UIMA
> Issue Type: Bug
> Components: Ruta
>Affects Versions: 2.8.0ruta
>Reporter: Michael Stenger
>Assignee: Peter Klügl
>Priority: Minor
> Fix For: 2.8.1ruta, 3.0.1ruta
>
>
> When list variables are declared with a list containing variables as initial
> value, the managing VariableListExpression seems to save the variable
> expression given with that argument list instead of the represented values.
> E.g.
> {code:java}
> INTLIST somelist = {var};{code}
> for a variable
> {code:java}
> INT var = 1;
> {code}
> stores the expression behind var instead of the value 1. So changing the
> value of var after the declaration of somelist still effects the value of
> somelist[0]. That's not the case if ADD was used instead.
> Consider this example:
> {code:java}
> DECLARE testType (StringArray arr);
> STRING s = "a";
> STRINGLIST sl = {s};
> Document{ -> ADD(sl, s), s = "b", CREATE(testType, "arr" = sl)};{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (UIMA-6192) VariableAssignmentExpression ignores List variables
[
https://issues.apache.org/jira/browse/UIMA-6192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Peter Klügl reassigned UIMA-6192:
-
Assignee: Peter Klügl
> VariableAssignmentExpression ignores List variables
> ---
>
> Key: UIMA-6192
> URL: https://issues.apache.org/jira/browse/UIMA-6192
> Project: UIMA
> Issue Type: Bug
> Components: Ruta
>Affects Versions: 2.8.0ruta
>Reporter: Michael Stenger
>Assignee: Peter Klügl
>Priority: Minor
> Fix For: 2.8.1ruta, 3.0.1ruta
>
>
> Action VariableAssignmentExpression seems to ignore the assignment task if a
> list variable is given as first argument. No exception is thrown, it just
> does nothing. Since action ASSIGN doesn't operate on list expressions too, it
> would be great to have this one working here.
> See the following example:
> {code:java}
> DECLARE testType (IntegerArray arr);
> INTLIST il;
> Document { -> il = {1,2,3}, CREATE(testType, "arr" = il)};{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (UIMA-6171) Ruta: Extend PARSE to work with annotation features
[ https://issues.apache.org/jira/browse/UIMA-6171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Klügl reassigned UIMA-6171: - Assignee: Peter Klügl > Ruta: Extend PARSE to work with annotation features > --- > > Key: UIMA-6171 > URL: https://issues.apache.org/jira/browse/UIMA-6171 > Project: UIMA > Issue Type: Improvement > Components: Ruta >Affects Versions: 3.0.0ruta, 2.8.0ruta >Reporter: Viorel Morari >Assignee: Peter Klügl >Priority: Major > Fix For: 2.8.1ruta, 3.0.1ruta > > > Currently, the PARSE condition takes the covered text of the matched > annotation as argument to be parsed. This issue suggests an improvement of > the PARSE condition to accept annotation features (e.g. Person.ageString) as > argument. -- This message was sent by Atlassian Jira (v8.3.4#803005)
