June 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-4270) Visual design: Highlighting treatment for GDST/DMN 7.5 Find results

by Elizabeth Clayton (Jira)

[ https://issues.jboss.org/browse/DROOLS-4270?page=com.atlassian.jira.plugi... ] Elizabeth Clayton updated DROOLS-4270: -------------------------------------- Description: As a user of the proposed 7.5 GDT/DMN "Find" feature, when I submit text using the find tool, I need to see the results visually highlighting in the respective canvas area. Find is a local search that could be performed in these areas of the application: * Guided Decision Table editor (tables) - Find text strings within "Data cells" * DMN graph * DMN boxed expressions (logic) - Find text strings within "Data cells" Requirements * Colors, etc for partial and whole text strings will need to be highlighted is required. * General recommendations regarding the usability and appearance for highlighting entire table cells and nodes. * Visual styles for the above if recommended. Considerations * Will not be able to leverage browser controls for Find. * Visual design should take into consideration the visual treatments that will be applied within these jiras: https://issues.jboss.org/browse/DROOLS-3953 and https://issues.jboss.org/browse/DROOLS-4258. was: This is a community epic for the [BAPL-1279|https://issues.jboss.org/browse/BAPL-1279]. The epic was created according to the [definition of ready|https://docs.google.com/document/d/1WKv_Cx7jCts7gCQCGt_323ANH_H7dv4...] that advices what needs to be agreed before each feature implementation. h1. Requirements See referenced document. h1. Documentation - Replace picture of GDT and DMN editor where they become obsolete h1. Acceptance test - Enter to large amount of data in search box - Search is possible when you type only the part of indicated word. For example, if you type text like 'test', the words 'testing', 'tester' should be displayed. - Searching for non-existing result - Result appearing once - Result appearing multiple times - Set of inputs: *- A-Z *- a-z *- 0-9 *- Symbols: } { ] [ ) ( ~ ! @ # $ % ^ & ` | \ : " ; ' < > ? , . ⁄ - + *- Blank spaces > Visual design: Highlighting treatment for GDST/DMN 7.5 Find results > ------------------------------------------------------------------- > > Key: DROOLS-4270 > URL: https://issues.jboss.org/browse/DROOLS-4270 > Project: Drools > Issue Type: Story > Components: DMN Editor > Affects Versions: 7.23.0.Final > Reporter: Elizabeth Clayton > Assignee: Elizabeth Clayton > Priority: Major > Labels: UX, UXTeam, drools-tools > Attachments: Example.png, Screen Shot 2019-05-30 at 5.14.30 PM.png > > > As a user of the proposed 7.5 GDT/DMN "Find" feature, when I submit text using the find tool, I need to see the results visually highlighting in the respective canvas area. > Find is a local search that could be performed in these areas of the application: > * Guided Decision Table editor (tables) > - Find text strings within "Data cells" > * DMN graph > * DMN boxed expressions (logic) > - Find text strings within "Data cells" > Requirements > * Colors, etc for partial and whole text strings will need to be highlighted is required. > * General recommendations regarding the usability and appearance for highlighting entire table cells and nodes. > * Visual styles for the above if recommended. > Considerations > * Will not be able to leverage browser controls for Find. > * Visual design should take into consideration the visual treatments that will be applied within these jiras: https://issues.jboss.org/browse/DROOLS-3953 and https://issues.jboss.org/browse/DROOLS-4258. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4270) Visual design: Highlighting treatment for GDST/DMN 7.5 Find results

by Elizabeth Clayton (Jira)

Elizabeth Clayton created DROOLS-4270: ----------------------------------------- Summary: Visual design: Highlighting treatment for GDST/DMN 7.5 Find results Key: DROOLS-4270 URL: https://issues.jboss.org/browse/DROOLS-4270 Project: Drools Issue Type: Story Components: DMN Editor Affects Versions: 7.23.0.Final Reporter: Elizabeth Clayton Assignee: Elizabeth Clayton Attachments: Example.png, Screen Shot 2019-05-30 at 5.14.30 PM.png This is a community epic for the [BAPL-1279|https://issues.jboss.org/browse/BAPL-1279]. The epic was created according to the [definition of ready|https://docs.google.com/document/d/1WKv_Cx7jCts7gCQCGt_323ANH_H7dv4...] that advices what needs to be agreed before each feature implementation. h1. Requirements See referenced document. h1. Documentation - Replace picture of GDT and DMN editor where they become obsolete h1. Acceptance test - Enter to large amount of data in search box - Search is possible when you type only the part of indicated word. For example, if you type text like 'test', the words 'testing', 'tester' should be displayed. - Searching for non-existing result - Result appearing once - Result appearing multiple times - Set of inputs: *- A-Z *- a-z *- 0-9 *- Symbols: } { ] [ ) ( ~ ! @ # $ % ^ & ` | \ : " ; ' < > ? , . ⁄ - + *- Blank spaces -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4270) Visual design: Highlighting treatment for GDST/DMN 7.5 Find results

by Elizabeth Clayton (Jira)

[ https://issues.jboss.org/browse/DROOLS-4270?page=com.atlassian.jira.plugi... ] Elizabeth Clayton updated DROOLS-4270: -------------------------------------- Story Points: (was: 8) > Visual design: Highlighting treatment for GDST/DMN 7.5 Find results > ------------------------------------------------------------------- > > Key: DROOLS-4270 > URL: https://issues.jboss.org/browse/DROOLS-4270 > Project: Drools > Issue Type: Story > Components: DMN Editor > Affects Versions: 7.23.0.Final > Reporter: Elizabeth Clayton > Assignee: Elizabeth Clayton > Priority: Major > Labels: UX, UXTeam, drools-tools > Attachments: Example.png, Screen Shot 2019-05-30 at 5.14.30 PM.png > > > This is a community epic for the [BAPL-1279|https://issues.jboss.org/browse/BAPL-1279]. The epic was created according to the [definition of ready|https://docs.google.com/document/d/1WKv_Cx7jCts7gCQCGt_323ANH_H7dv4...] that advices what needs to be agreed before each feature implementation. > h1. Requirements > See referenced document. > h1. Documentation > - Replace picture of GDT and DMN editor where they become obsolete > h1. Acceptance test > - Enter to large amount of data in search box > - Search is possible when you type only the part of indicated word. For example, if you type text like 'test', the words 'testing', 'tester' should be displayed. > - Searching for non-existing result > - Result appearing once > - Result appearing multiple times > - Set of inputs: > *- A-Z > *- a-z > *- 0-9 > *- Symbols: } { ] [ ) ( ~ ! @ # $ % ^ & ` | \ : " ; ' < > ? , . ⁄ - + > *- Blank spaces -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12226) IJ020017: Invalid archive: file://RaActivatoractivemq-ra WARN during start with standalone-full*.xml

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFLY-12226?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFLY-12226: ------------------------------------ Fix Version/s: 17.0.1.Final 18.0.0.Beta1 > IJ020017: Invalid archive: file://RaActivatoractivemq-ra WARN during start with standalone-full*.xml > ---------------------------------------------------------------------------------------------------- > > Key: WFLY-12226 > URL: https://issues.jboss.org/browse/WFLY-12226 > Project: WildFly > Issue Type: Bug > Components: JMS > Affects Versions: 18.0.0.Beta1 > Reporter: Ondrej Kotek > Assignee: Emmanuel Hugonnet > Priority: Critical > Fix For: 17.0.1.Final, 18.0.0.Beta1 > > > There is a warning during start with standalone-full*.xml: > {noformat} > 12:19:04,432 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-3) WFLYJCA0007: Registered connection factory java:/JmsXA > 12:19:04,440 INFO [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 84) WFLYMSGAMQ0002: Bound messaging object to jndi name java:jboss/exported/jms/RemoteConnectionFactory > 12:19:04,441 INFO [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 83) WFLYMSGAMQ0002: Bound messaging object to jndi name java:/ConnectionFactory > 12:19:04,441 WARN [org.jboss.as.connector.services.resourceadapters.ResourceAdapterActivatorService$ResourceAdapterActivator] (MSC service thread 1-3) IJ020017: Invalid archive: file://RaActivatoractivemq-ra > 12:19:04,486 INFO [org.apache.activemq.artemis.ra] (MSC service thread 1-3) AMQ151007: Resource adaptor started > 12:19:04,486 INFO [org.jboss.as.connector.services.resourceadapters.ResourceAdapterActivatorService$ResourceAdapterActivator] (MSC service thread 1-3) IJ020002: Deployed: file://RaActivatoractivemq-ra > 12:19:04,492 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-6) WFLYJCA0002: Bound JCA ConnectionFactory [java:/JmsXA] > 12:19:04,493 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-3) WFLYJCA0118: Binding connection factory named java:/JmsXA to alias java:jboss/DefaultJMSConnectionFactory > {noformat} > For an automation checking the server log for issues, this WARN causes false positive. Hence, I set the Priority to Critical. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12257) Memory leak in wildfly transaction client

by Cheng Fang (Jira)

Cheng Fang created WFLY-12257: --------------------------------- Summary: Memory leak in wildfly transaction client Key: WFLY-12257 URL: https://issues.jboss.org/browse/WFLY-12257 Project: WildFly Issue Type: Bug Components: Transactions Affects Versions: 15.0.1.Final Environment: wildfly-transaction-client-1.1.3.Final wildfly.15.0.1.Final Windows 10 Reporter: Cheng Fang Assignee: Cheng Fang After a volume run of our system we recognized millions of entries in the openFilePaths Object of class FileSystemXAResourceRegistry. When enabling traces for org.wildfly.transaction it seems that for adding an entry a xid string is used {code:java} XAResourceRegistryFile(Xid xid) throws SystemException { xaRecoveryPath.toFile().mkdir(); // create dir if non existent final String xidString = SimpleXid.of(xid).toHexString('_'); this.filePath = xaRecoveryPath.resolve(xidString); openFilePaths.add(*xidString*); {code} and for removing the entire file path: {code:java} protected void removeResource(XAResource resource) throws XAException { if (resources.remove(resource)) { if (resources.isEmpty()) { // delete file try { if (fileChannel != null) { fileChannel.close(); } Files.delete(filePath); // deleting using the filepath as key caused a memory leak, // if xid string have been added, therefore build the xid string for removing openFilePaths.remove(*filePath.toString()*); {code} We didn't find any code where this xid are cleaned up. As workaround we additionally extract the xid String from the file path and remove the corresponding entry. {code:java} String xidString = filePath.toString().substring(filePath.toString().indexOf( xaRecoveryPath.toString()) + xaRecoveryPath.toString().length() + 1); openFilePaths.remove(xidString); {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12256) Upgrade WildFly Core to 9.0.2.Final

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFLY-12256?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFLY-12256: ------------------------------------ Fix Version/s: 17.0.1.Final 18.0.0.Beta1 I put both the 17.0.1.Final and 18.0.0.Beta1 fix versions on this, but it's ok to drop 18.0.0.Beta1 if there will be a core 10.0.0.Beta1 to put into master next week. > Upgrade WildFly Core to 9.0.2.Final > ----------------------------------- > > Key: WFLY-12256 > URL: https://issues.jboss.org/browse/WFLY-12256 > Project: WildFly > Issue Type: Component Upgrade > Components: Server > Reporter: Brian Stansberry > Assignee: Jeff Mesnil > Priority: Major > Fix For: 17.0.1.Final, 18.0.0.Beta1 > > > Move to 9.0.2.Final. > https://issues.jboss.org/projects/WFCORE/versions/12342214 -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12256) Upgrade WildFly Core to 9.0.2.Final

by Brian Stansberry (Jira)

Brian Stansberry created WFLY-12256: --------------------------------------- Summary: Upgrade WildFly Core to 9.0.2.Final Key: WFLY-12256 URL: https://issues.jboss.org/browse/WFLY-12256 Project: WildFly Issue Type: Component Upgrade Components: Server Reporter: Brian Stansberry Assignee: Jeff Mesnil Move to 9.0.2.Final. https://issues.jboss.org/projects/WFCORE/versions/12342214 -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-793) Migrate KprodM to PSI Cluster

by Matthew Mahoney (Jira)

[ https://issues.jboss.org/browse/SWSQE-793?page=com.atlassian.jira.plugin.... ] Matthew Mahoney updated SWSQE-793: ---------------------------------- Sprint: Kiali Sprint #23, Kiali Sprint #25 (was: Kiali Sprint #23, Kiali Sprint #24) > Migrate KprodM to PSI Cluster > ----------------------------- > > Key: SWSQE-793 > URL: https://issues.jboss.org/browse/SWSQE-793 > Project: Kiali QE > Issue Type: QE Task > Reporter: Matthew Mahoney > Assignee: Matthew Mahoney > Priority: Major > Labels: infrastructure > > The KProdM cluster is 3.11. Time to migrate to OCP4.1. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-795) Porting back install-maistra-upstream to Istio-Kiali-on-Openshift Job

by Matthew Mahoney (Jira)

[ https://issues.jboss.org/browse/SWSQE-795?page=com.atlassian.jira.plugin.... ] Matthew Mahoney updated SWSQE-795: ---------------------------------- Sprint: Kiali Sprint #25 (was: Kiali Sprint #24) > Porting back install-maistra-upstream to Istio-Kiali-on-Openshift Job > --------------------------------------------------------------------- > > Key: SWSQE-795 > URL: https://issues.jboss.org/browse/SWSQE-795 > Project: Kiali QE > Issue Type: Task > Reporter: Guilherme Baufaker Rêgo > Priority: Major > Labels: infrastructure > -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-783) Review and Create new Kiali Install/Deploy Test Cases

by Matthew Mahoney (Jira)

[ https://issues.jboss.org/browse/SWSQE-783?page=com.atlassian.jira.plugin.... ] Matthew Mahoney updated SWSQE-783: ---------------------------------- Sprint: Kiali Sprint #23, Kiali Sprint #25 (was: Kiali Sprint #23, Kiali Sprint #24) > Review and Create new Kiali Install/Deploy Test Cases > ----------------------------------------------------- > > Key: SWSQE-783 > URL: https://issues.jboss.org/browse/SWSQE-783 > Project: Kiali QE > Issue Type: QE Task > Reporter: Matthew Mahoney > Priority: Major > Labels: pqi > > Currently there is 1 Polarion Install test case. Review this test case and separate into multiple test cases, as needed. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 3 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira June 2019