[jira] [Resolved] (UIMA-5117) UIMA-AS: dd2spring should log at INFO
[ https://issues.apache.org/jira/browse/UIMA-5117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Burn Lewis resolved UIMA-5117. -- Resolution: Fixed Log errors at SEVERE level. Use a shutdown hook to report when saxon calls exit. Fix the "net.sf.saxon.event.MessageEmitter is not a Receiver" error by not using a classloader if saxon is already in the classpath > UIMA-AS: dd2spring should log at INFO > - > > Key: UIMA-5117 > URL: https://issues.apache.org/jira/browse/UIMA-5117 > Project: UIMA > Issue Type: Bug > Components: Async Scaleout >Reporter: Jerry Cwiklik >Assignee: Burn Lewis > Fix For: 2.9.0AS > > > Dd2Spring.convertDd2Spring() method should log exceptions at INFO level > instead of CONFIG. When runtime was mis-configured, the code was failing yet > there were no exceptions being logged, making debugging difficult. > Also, when exception happens in converDd2Spring() it is not being re-thrown. > This causes the uima-as to continue running and trying to deploy using > zero-length spring context file which results in another Exception. Modify > code to re-throw Exception. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (UIMA-5117) UIMA-AS: dd2spring should log at INFO
[ https://issues.apache.org/jira/browse/UIMA-5117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Burn Lewis closed UIMA-5117. > UIMA-AS: dd2spring should log at INFO > - > > Key: UIMA-5117 > URL: https://issues.apache.org/jira/browse/UIMA-5117 > Project: UIMA > Issue Type: Bug > Components: Async Scaleout >Reporter: Jerry Cwiklik >Assignee: Burn Lewis > Fix For: 2.9.0AS > > > Dd2Spring.convertDd2Spring() method should log exceptions at INFO level > instead of CONFIG. When runtime was mis-configured, the code was failing yet > there were no exceptions being logged, making debugging difficult. > Also, when exception happens in converDd2Spring() it is not being re-thrown. > This causes the uima-as to continue running and trying to deploy using > zero-length spring context file which results in another Exception. Modify > code to re-throw Exception. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Reopened] (UIMA-5117) UIMA-AS: dd2spring should log at INFO
[ https://issues.apache.org/jira/browse/UIMA-5117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Burn Lewis reopened UIMA-5117: -- Assignee: Burn Lewis (was: Jerry Cwiklik) Perhaps better to log these failures as SEVERE. Also would be nice to know when saxon calls exit ... and why! > UIMA-AS: dd2spring should log at INFO > - > > Key: UIMA-5117 > URL: https://issues.apache.org/jira/browse/UIMA-5117 > Project: UIMA > Issue Type: Bug > Components: Async Scaleout >Reporter: Jerry Cwiklik >Assignee: Burn Lewis > Fix For: 2.9.0AS > > > Dd2Spring.convertDd2Spring() method should log exceptions at INFO level > instead of CONFIG. When runtime was mis-configured, the code was failing yet > there were no exceptions being logged, making debugging difficult. > Also, when exception happens in converDd2Spring() it is not being re-thrown. > This causes the uima-as to continue running and trying to deploy using > zero-length spring context file which results in another Exception. Modify > code to re-throw Exception. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: [jira] [Commented] (UIMA-5116) CVD tiny font size on hidpi monitor
Great! Thanks :-) -Marshall On 9/22/2016 11:37 AM, Jessica Glover wrote: > Hi Marshall, > > Thanks for your response. It *should* be platform agnostic, since I'm > deriving font size for Swing components from the system look and feel. I > hadn't had a chance to do it yet, but I'll definitely test on different > platforms before submitting the patch. > > Thanks, > Jessica > > On Thu, Sep 22, 2016 at 9:20 AM, Marshall Schor (JIRA) > wrote: > >> [ https://issues.apache.org/jira/browse/UIMA-5116?page= >> com.atlassian.jira.plugin.system.issuetabpanels:comment- >> tabpanel&focusedCommentId=15513286#comment-15513286 ] >> >> Marshall Schor commented on UIMA-5116: >> -- >> >> a patch would be appreciated. Is it platform (Windows, Linux, MacOS, >> etc.) agnostic? >> >>> CVD tiny font size on hidpi monitor >>> --- >>> >>> Key: UIMA-5116 >>> URL: https://issues.apache.org/jira/browse/UIMA-5116 >>> Project: UIMA >>> Issue Type: Bug >>> Components: Tools >>> Environment: Windows 10, 276 ppi monitor. >>>Reporter: Jessica Glover >>>Priority: Minor >>> >>> On Windows 10, with a high dpi monitor, the CVD appears in a very small >> window. When the window is resized, the font is still unreadably small. >>> On my local machine, I ran the CVD with system look and feel. This >> increased the font size for the pane labels, but not the text inside the >> text display. >>> In the CVD class, I updated the main method to reset the UIManager >> defaults for TextArea.font and Tree.font to match TextField.font. This >> fixed the font size of the text, but the text in the IR and FS trees was >> being cut off on the top and bottom. >>> In the MainFrame class, I updated the height of the tree rows in >> initFSTree() and initIRTree() to be the same as the fsTree font size. It >> needs to be increased just a tad, but otherwise the display looks great now. >>> Not sure whether I should submit a patch, or if there is a better >> approach to ensure continued compatibility with other systems. >> >> >> >> -- >> This message was sent by Atlassian JIRA >> (v6.3.4#6332) >>
[jira] [Commented] (UIMA-5117) UIMA-AS: dd2spring should log at INFO
[ https://issues.apache.org/jira/browse/UIMA-5117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15514328#comment-15514328 ] Burn Lewis commented on UIMA-5117: -- Since this is a serious error shouldn't we log at SEVERE rather than INFO? Also no need to catch the 3 specific exceptions since we log the same message ... just Exception would be enough. But in the case that triggered this investigation the log level didn't matter as even the stack trace was not printed, apparently because saxon calls System.exit() on some errors. It also prints a cryptic error message "net.sf.saxon.event.MessageEmitter is not a Receiver" that for some reason is not always captured. The real problem is that UIMA-AS uses a classloader to load the Transform class from saxon8.jar but if that jar is also in the users's classpath there will be an incompatibility between classes loaded from each jar making it appear that the MessageEmiiter class does not implement the Receiver interface. We should omit the special classloader if saxon8 is already in the classpath. > UIMA-AS: dd2spring should log at INFO > - > > Key: UIMA-5117 > URL: https://issues.apache.org/jira/browse/UIMA-5117 > Project: UIMA > Issue Type: Bug > Components: Async Scaleout >Reporter: Jerry Cwiklik >Assignee: Jerry Cwiklik > Fix For: 2.9.0AS > > > Dd2Spring.convertDd2Spring() method should log exceptions at INFO level > instead of CONFIG. When runtime was mis-configured, the code was failing yet > there were no exceptions being logged, making debugging difficult. > Also, when exception happens in converDd2Spring() it is not being re-thrown. > This causes the uima-as to continue running and trying to deploy using > zero-length spring context file which results in another Exception. Modify > code to re-throw Exception. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (UIMA-5118) UIMA-AS: NPE thrown when cleaning up C++ based service
[ https://issues.apache.org/jira/browse/UIMA-5118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jerry Cwiklik closed UIMA-5118. --- Resolution: Fixed added check for null to avoid NPE > UIMA-AS: NPE thrown when cleaning up C++ based service > -- > > Key: UIMA-5118 > URL: https://issues.apache.org/jira/browse/UIMA-5118 > Project: UIMA > Issue Type: Bug > Components: Async Scaleout >Reporter: Jerry Cwiklik >Assignee: Jerry Cwiklik > Fix For: 2.9.0AS > > > NPE is thrown from BaseUIMAAsynchronousEngine_impl.undeploy() > line: > ((AnalysisEngineController) ctrer).getControllerLatch().release(); > > when a controller is an instance of UimacppServiceController. This class > returns null from getControllerLatch() causing NPE in the uima-as client > which tries to clean up after processing. > Add check for null before attempting call to release(). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (UIMA-5118) UIMA-AS: NPE thrown when cleaning up C++ based service
Jerry Cwiklik created UIMA-5118: --- Summary: UIMA-AS: NPE thrown when cleaning up C++ based service Key: UIMA-5118 URL: https://issues.apache.org/jira/browse/UIMA-5118 Project: UIMA Issue Type: Bug Components: Async Scaleout Reporter: Jerry Cwiklik Assignee: Jerry Cwiklik Fix For: 2.9.0AS NPE is thrown from BaseUIMAAsynchronousEngine_impl.undeploy() line: ((AnalysisEngineController) ctrer).getControllerLatch().release(); when a controller is an instance of UimacppServiceController. This class returns null from getControllerLatch() causing NPE in the uima-as client which tries to clean up after processing. Add check for null before attempting call to release(). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (UIMA-5117) UIMA-AS: dd2spring should log at INFO
[ https://issues.apache.org/jira/browse/UIMA-5117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jerry Cwiklik closed UIMA-5117. --- Resolution: Fixed modified to re-throw exceptions and log them > UIMA-AS: dd2spring should log at INFO > - > > Key: UIMA-5117 > URL: https://issues.apache.org/jira/browse/UIMA-5117 > Project: UIMA > Issue Type: Bug > Components: Async Scaleout >Reporter: Jerry Cwiklik >Assignee: Jerry Cwiklik > Fix For: 2.9.0AS > > > Dd2Spring.convertDd2Spring() method should log exceptions at INFO level > instead of CONFIG. When runtime was mis-configured, the code was failing yet > there were no exceptions being logged, making debugging difficult. > Also, when exception happens in converDd2Spring() it is not being re-thrown. > This causes the uima-as to continue running and trying to deploy using > zero-length spring context file which results in another Exception. Modify > code to re-throw Exception. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: [jira] [Commented] (UIMA-5116) CVD tiny font size on hidpi monitor
Hi Marshall, Thanks for your response. It *should* be platform agnostic, since I'm deriving font size for Swing components from the system look and feel. I hadn't had a chance to do it yet, but I'll definitely test on different platforms before submitting the patch. Thanks, Jessica On Thu, Sep 22, 2016 at 9:20 AM, Marshall Schor (JIRA) wrote: > > [ https://issues.apache.org/jira/browse/UIMA-5116?page= > com.atlassian.jira.plugin.system.issuetabpanels:comment- > tabpanel&focusedCommentId=15513286#comment-15513286 ] > > Marshall Schor commented on UIMA-5116: > -- > > a patch would be appreciated. Is it platform (Windows, Linux, MacOS, > etc.) agnostic? > > > CVD tiny font size on hidpi monitor > > --- > > > > Key: UIMA-5116 > > URL: https://issues.apache.org/jira/browse/UIMA-5116 > > Project: UIMA > > Issue Type: Bug > > Components: Tools > > Environment: Windows 10, 276 ppi monitor. > >Reporter: Jessica Glover > >Priority: Minor > > > > On Windows 10, with a high dpi monitor, the CVD appears in a very small > window. When the window is resized, the font is still unreadably small. > > On my local machine, I ran the CVD with system look and feel. This > increased the font size for the pane labels, but not the text inside the > text display. > > In the CVD class, I updated the main method to reset the UIManager > defaults for TextArea.font and Tree.font to match TextField.font. This > fixed the font size of the text, but the text in the IR and FS trees was > being cut off on the top and bottom. > > In the MainFrame class, I updated the height of the tree rows in > initFSTree() and initIRTree() to be the same as the fsTree font size. It > needs to be increased just a tad, but otherwise the display looks great now. > > Not sure whether I should submit a patch, or if there is a better > approach to ensure continued compatibility with other systems. > > > > -- > This message was sent by Atlassian JIRA > (v6.3.4#6332) >
[jira] [Updated] (UIMA-5117) UIMA-AS: dd2spring should log at INFO
[ https://issues.apache.org/jira/browse/UIMA-5117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jerry Cwiklik updated UIMA-5117: Description: Dd2Spring.convertDd2Spring() method should log exceptions at INFO level instead of CONFIG. When runtime was mis-configured, the code was failing yet there were no exceptions being logged, making debugging difficult. Also, when exception happens in converDd2Spring() it is not being re-thrown. This causes the uima-as to continue running and trying to deploy using zero-length spring context file which results in another Exception. Modify code to re-throw Exception. was: Dd2Spring.convertDd2Spring() method should log exceptions at INFO level instead of CONFIG. When runtime was mis-configured, the code was failing yet there were no exceptions being logged, making debugging difficult. > UIMA-AS: dd2spring should log at INFO > - > > Key: UIMA-5117 > URL: https://issues.apache.org/jira/browse/UIMA-5117 > Project: UIMA > Issue Type: Bug > Components: Async Scaleout >Reporter: Jerry Cwiklik >Assignee: Jerry Cwiklik > Fix For: 2.9.0AS > > > Dd2Spring.convertDd2Spring() method should log exceptions at INFO level > instead of CONFIG. When runtime was mis-configured, the code was failing yet > there were no exceptions being logged, making debugging difficult. > Also, when exception happens in converDd2Spring() it is not being re-thrown. > This causes the uima-as to continue running and trying to deploy using > zero-length spring context file which results in another Exception. Modify > code to re-throw Exception. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (UIMA-5115) uv3 select() api for iterators and streams over CAS contents
[ https://issues.apache.org/jira/browse/UIMA-5115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15513597#comment-15513597 ] Richard Eckart de Castilho commented on UIMA-5115: -- I think it is not an unusual case to ask for "for the given Lemma, give me all other Lemmas at the same location" - so I think only the reference annotation itself should be excluded from the result of a covering/coveredBy/at but not other annotations of the same type... > uv3 select() api for iterators and streams over CAS contents > > > Key: UIMA-5115 > URL: https://issues.apache.org/jira/browse/UIMA-5115 > Project: UIMA > Issue Type: New Feature > Components: Core Java Framework >Reporter: Marshall Schor >Priority: Minor > Fix For: 3.0.0SDKexp > > > Design and implement a select() API based on uimaFIT's select, integrated > well with Java 8 concepts. Initial discussions in UIMA-1524. Wiki with > diagram: https://cwiki.apache.org/confluence/display/UIMA/UV3+Iterator+support -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (UIMA-5115) uv3 select() api for iterators and streams over CAS contents
[ https://issues.apache.org/jira/browse/UIMA-5115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15513511#comment-15513511 ] Marshall Schor commented on UIMA-5115: -- For the prototype, I'm doing all variants. Default is the uimaFIT style (this can be adjusted, based on community feedback). The variants are controlled by the builder methods: * typePriority - to use type priority as part of the comparator for position and bounds; default is not to * positionUsesType - when type priority is not used, use the type as part of the "equals" when positioning to the left most among equals; default is not to * skipEqual - for boundedBy, bounding, at: skip returning FSs which are "equal"; default: skip FSs which has same ID as bounding FS. ** Note: the at(FSp) with skipEqual is non empty only for typePriority or positionUsesType cases, in which case it returns Annotations with the same begin/end, but with different types than FSp. > uv3 select() api for iterators and streams over CAS contents > > > Key: UIMA-5115 > URL: https://issues.apache.org/jira/browse/UIMA-5115 > Project: UIMA > Issue Type: New Feature > Components: Core Java Framework >Reporter: Marshall Schor >Priority: Minor > Fix For: 3.0.0SDKexp > > > Design and implement a select() API based on uimaFIT's select, integrated > well with Java 8 concepts. Initial discussions in UIMA-1524. Wiki with > diagram: https://cwiki.apache.org/confluence/display/UIMA/UV3+Iterator+support -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (UIMA-5115) uv3 select() api for iterators and streams over CAS contents
[ https://issues.apache.org/jira/browse/UIMA-5115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15513455#comment-15513455 ] Marshall Schor commented on UIMA-5115: -- Details of positioning and bounds, with and without typePriorities: Here's how I think uimaFIT currently is implemented: * (Assume FSp is the FeatureStructure being used as a position, or as a bound) * The type of FSp is ignored; only the begin/end values are used * The starting position is the first (left-most) FS >= FSp (using just begin/end) ** In the case where there are multiple FSs with the same begin/end as FSp, the starting position is the left-most one of these * For bounding operations, if there is an FS which is exactly equal (has the same "id") to FSp, it is skipped. ** Because of the left-most rule, the bounding operation might return fsA, fsB, (skip fsC which has the same *id* as FSp), fsD, etc. Here's a proposal of how this would work with typePriorities (this is different from how subiterator works, see following): * The type of FSp is used as part of the comparison, using the AnnotationIndex comparator * The rest of the definition is as above, except that the comparisons use the typePriorities Subiterator uses this logic: * It always uses type priorities * For positioning, it works as above (type priority case) * For bounding operations: it first positions using the FSp, and then advances until it finds the first FS not equal (using begin/end/type), and starts there Subiterator style, without typePriority (not currently available, here's a proposed design consistent with the subiterator style): * For positioning the first (left-most) FS >= FSp (using just begin/end) * For bounding operations, it first positions using the FSp, then advances until it finds the first FS not equal (using just begin/end), and starts there. The differences between the subiterator / uimaFIT approaches (for corresponding typePriority use or not) may be accidental artifacts of implementation. Should we make the uv3 select() implementation for bounding operations: * skip the FS which has the same id (only) [ uimaFIT sytle ] or * skip all FSs until finding the first one > than FSp (using either begin/end/type or just begin/end) [ subiterator sytle ] I would like to hear from the user community, too :-) > uv3 select() api for iterators and streams over CAS contents > > > Key: UIMA-5115 > URL: https://issues.apache.org/jira/browse/UIMA-5115 > Project: UIMA > Issue Type: New Feature > Components: Core Java Framework >Reporter: Marshall Schor >Priority: Minor > Fix For: 3.0.0SDKexp > > > Design and implement a select() API based on uimaFIT's select, integrated > well with Java 8 concepts. Initial discussions in UIMA-1524. Wiki with > diagram: https://cwiki.apache.org/confluence/display/UIMA/UV3+Iterator+support -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (UIMA-5116) CVD tiny font size on hidpi monitor
[ https://issues.apache.org/jira/browse/UIMA-5116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15513286#comment-15513286 ] Marshall Schor commented on UIMA-5116: -- a patch would be appreciated. Is it platform (Windows, Linux, MacOS, etc.) agnostic? > CVD tiny font size on hidpi monitor > --- > > Key: UIMA-5116 > URL: https://issues.apache.org/jira/browse/UIMA-5116 > Project: UIMA > Issue Type: Bug > Components: Tools > Environment: Windows 10, 276 ppi monitor. >Reporter: Jessica Glover >Priority: Minor > > On Windows 10, with a high dpi monitor, the CVD appears in a very small > window. When the window is resized, the font is still unreadably small. > On my local machine, I ran the CVD with system look and feel. This increased > the font size for the pane labels, but not the text inside the text display. > In the CVD class, I updated the main method to reset the UIManager defaults > for TextArea.font and Tree.font to match TextField.font. This fixed the font > size of the text, but the text in the IR and FS trees was being cut off on > the top and bottom. > In the MainFrame class, I updated the height of the tree rows in initFSTree() > and initIRTree() to be the same as the fsTree font size. It needs to be > increased just a tad, but otherwise the display looks great now. > Not sure whether I should submit a patch, or if there is a better approach to > ensure continued compatibility with other systems. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
