October 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-2926) Make the old panel reusable (move to kie-wb-common-ui) and use it on both old and new test scenarios

by Toni Rikkola (Jira)

[ https://issues.jboss.org/browse/DROOLS-2926?page=com.atlassian.jira.plugi... ] Toni Rikkola reassigned DROOLS-2926: ------------------------------------ Assignee: Toni Rikkola (was: Juraj Soltes) > Make the old panel reusable (move to kie-wb-common-ui) and use it on both old and new test scenarios > ---------------------------------------------------------------------------------------------------- > > Key: DROOLS-2926 > URL: https://issues.jboss.org/browse/DROOLS-2926 > Project: Drools > Issue Type: Sub-task > Components: Scenario Simulation and Testing > Reporter: Juraj Soltes > Assignee: Toni Rikkola > Priority: Major > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3096) This epic groups items that cannot be implemented for MVP

by Daniele Zonca (Jira)

[ https://issues.jboss.org/browse/DROOLS-3096?page=com.atlassian.jira.plugi... ] Daniele Zonca reassigned DROOLS-3096: ------------------------------------- Assignee: Daniele Zonca (was: Mario Fusco) > This epic groups items that cannot be implemented for MVP > --------------------------------------------------------- > > Key: DROOLS-3096 > URL: https://issues.jboss.org/browse/DROOLS-3096 > Project: Drools > Issue Type: Epic > Components: Scenario Simulation and Testing > Reporter: Daniele Zonca > Assignee: Daniele Zonca > Priority: Major > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11154) mod_cluster reports "Starting to drain 1 active sessions from (...) in 0 seconds." even when it waits indefinitely

by Jan Kašík (Jira)

[ https://issues.jboss.org/browse/WFLY-11154?page=com.atlassian.jira.plugin... ] Jan Kašík updated WFLY-11154: ----------------------------- Description: When {{stop}} operation with {{waittime=0}} is called on a mod_cluster node, it wait indefinitely until all sessions time out. However, following line appears in log: {code} INFO [org.jboss.modcluster] (management-handler-thread - 1) MODCLUSTER000046: Starting to drain 1 active sessions from default-host:/karel in 0 seconds. {code} This could confuse someone looking into the log -- they would then think,that this operation killed sessions even when it didn't. Suggestion: Replace this message with more accurate one. was: When {{stop}} operation with {{waittime=0}} is called on node, it wait indefinitely until all sessions time out. However, following line appears in log: {code} INFO [org.jboss.modcluster] (management-handler-thread - 1) MODCLUSTER000046: Starting to drain 1 active sessions from default-host:/karel in 0 seconds. {code} This could confuse someone looking into the log -- they would then think,that this operation killed sessions even when it didn't. Suggestion: Replace this message with more accurate one. > mod_cluster reports "Starting to drain 1 active sessions from (...) in 0 seconds." even when it waits indefinitely > ------------------------------------------------------------------------------------------------------------------ > > Key: WFLY-11154 > URL: https://issues.jboss.org/browse/WFLY-11154 > Project: WildFly > Issue Type: Bug > Components: mod_cluster > Affects Versions: 14.0.0.Final, 15.0.0.Alpha1 > Reporter: Jan Kašík > Assignee: Radoslav Husar > Priority: Optional > > When {{stop}} operation with {{waittime=0}} is called on a mod_cluster node, it wait indefinitely until all sessions time out. However, following line appears in log: > {code} > INFO [org.jboss.modcluster] (management-handler-thread - 1) MODCLUSTER000046: Starting to drain 1 active sessions from default-host:/karel in 0 seconds. > {code} > This could confuse someone looking into the log -- they would then think,that this operation killed sessions even when it didn't. > Suggestion: Replace this message with more accurate one. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11154) mod_cluster reports "Starting to drain 1 active sessions from (...) in 0 seconds." even when it waits indefinitely

by Jan Kašík (Jira)

Jan Kašík created WFLY-11154: -------------------------------- Summary: mod_cluster reports "Starting to drain 1 active sessions from (...) in 0 seconds." even when it waits indefinitely Key: WFLY-11154 URL: https://issues.jboss.org/browse/WFLY-11154 Project: WildFly Issue Type: Bug Components: mod_cluster Affects Versions: 14.0.0.Final, 15.0.0.Alpha1 Reporter: Jan Kašík Assignee: Radoslav Husar When {{stop}} operation with {{waittime=0}} is called on node, it wait indefinitely until all sessions time out. However, following line appears in log: {code} INFO [org.jboss.modcluster] (management-handler-thread - 1) MODCLUSTER000046: Starting to drain 1 active sessions from default-host:/karel in 0 seconds. {code} This could confuse someone looking into the log -- they would then think,that this operation killed sessions even when it didn't. Suggestion: Replace this message with more accurate one. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10178) Introduce general support for MR JARs into parent POM

by Rostislav Svoboda (Jira)

[ https://issues.jboss.org/browse/WFLY-10178?page=com.atlassian.jira.plugin... ] Rostislav Svoboda commented on WFLY-10178: ------------------------------------------ [~dmlloyd] I think you can set yourself back as assignee. I see you prepared https://github.com/jboss/jboss-parent-pom/pull/53 > Introduce general support for MR JARs into parent POM > ----------------------------------------------------- > > Key: WFLY-10178 > URL: https://issues.jboss.org/browse/WFLY-10178 > Project: WildFly > Issue Type: Enhancement > Components: Build System > Reporter: David Lloyd > Priority: Major > > Backing issue for design proposal to introduce MR JAR support into jboss-parent, so WFLY, WFCORE, and all other subprojects which consume jboss-parent can support MR JARs without any extra work. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3024) [DMN Designer] Data Types - Add nested data types

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-3024?page=com.atlassian.jira.plugi... ] Jozef Marko commented on DROOLS-3024: ------------------------------------- Founding No.2 In the well known dmn model [^DMCommunity Challenge - March 2017.dmn] if I insert or remove field that is in some nested level, the operation slow down rapidly. For example insert field field above *Minimum Matching Interest* of *tCandidate > Profile 2* takes about 2 seconds what is not ideal for such small model. Are we aware of this? Same for remove action. > [DMN Designer] Data Types - Add nested data types > ------------------------------------------------- > > Key: DROOLS-3024 > URL: https://issues.jboss.org/browse/DROOLS-3024 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Guilherme Carreiro > Assignee: Guilherme Carreiro > Priority: Major > Labels: drools-tools > Attachments: DMCommunity Challenge - March 2017.dmn, options.png > > > - The user must be able to insert a new field (Data Type) above, below and nested, as the options listed in the kebab menu: > !options.png|thumbnail! > h2. Manual Acceptance Test > h3. Insert above > - on top level (/) > - on the nested level (/) > - on the deepest level (/) > - no warning in browser console (/) > h3. Insert below > - on top level > - on the nested level > - on the deepest level > - no warning in browser console > h3. Insert nested > - on top level > - on the nested level > - on the deepest level > - no warning in browser console > h3. Build and deploy > - Build and deploy model that uses new created data type -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3024) [DMN Designer] Data Types - Add nested data types

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-3024?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-3024: -------------------------------- Attachment: DMCommunity Challenge - March 2017.dmn > [DMN Designer] Data Types - Add nested data types > ------------------------------------------------- > > Key: DROOLS-3024 > URL: https://issues.jboss.org/browse/DROOLS-3024 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Guilherme Carreiro > Assignee: Guilherme Carreiro > Priority: Major > Labels: drools-tools > Attachments: DMCommunity Challenge - March 2017.dmn, options.png > > > - The user must be able to insert a new field (Data Type) above, below and nested, as the options listed in the kebab menu: > !options.png|thumbnail! > h2. Manual Acceptance Test > h3. Insert above > - on top level (/) > - on the nested level (/) > - on the deepest level (/) > - no warning in browser console (/) > h3. Insert below > - on top level > - on the nested level > - on the deepest level > - no warning in browser console > h3. Insert nested > - on top level > - on the nested level > - on the deepest level > - no warning in browser console > h3. Build and deploy > - Build and deploy model that uses new created data type -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3024) [DMN Designer] Data Types - Add nested data types

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-3024?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-3024: -------------------------------- Description: - The user must be able to insert a new field (Data Type) above, below and nested, as the options listed in the kebab menu: !options.png|thumbnail! h2. Manual Acceptance Test h3. Insert above - on top level (/) - on the nested level (/) - on the deepest level (/) - no warning in browser console (/) h3. Insert below - on top level - on the nested level - on the deepest level - no warning in browser console h3. Insert nested - on top level - on the nested level - on the deepest level - no warning in browser console h3. Build and deploy - Build and deploy model that uses new created data type was: - The user must be able to insert a new field (Data Type) above, below and nested, as the options listed in the kebab menu: !options.png|thumbnail! h2. Manual Acceptance Test h3. Insert above - on top level - on the nested level - on the deepest level - no warning in browser console h3. Insert below - on top level - on the nested level - on the deepest level - no warning in browser console h3. Insert nested - on top level - on the nested level - on the deepest level - no warning in browser console h3. Build and deploy - Build and deploy model that uses new created data type > [DMN Designer] Data Types - Add nested data types > ------------------------------------------------- > > Key: DROOLS-3024 > URL: https://issues.jboss.org/browse/DROOLS-3024 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Guilherme Carreiro > Assignee: Guilherme Carreiro > Priority: Major > Labels: drools-tools > Attachments: options.png > > > - The user must be able to insert a new field (Data Type) above, below and nested, as the options listed in the kebab menu: > !options.png|thumbnail! > h2. Manual Acceptance Test > h3. Insert above > - on top level (/) > - on the nested level (/) > - on the deepest level (/) > - no warning in browser console (/) > h3. Insert below > - on top level > - on the nested level > - on the deepest level > - no warning in browser console > h3. Insert nested > - on top level > - on the nested level > - on the deepest level > - no warning in browser console > h3. Build and deploy > - Build and deploy model that uses new created data type -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-453) Checker job - Skip Terminating Kiali

by Hayk Hovsepyan (Jira)

[ https://issues.jboss.org/browse/SWSQE-453?page=com.atlassian.jira.plugin.... ] Hayk Hovsepyan updated SWSQE-453: --------------------------------- Priority: Blocker (was: Major) > Checker job - Skip Terminating Kiali > ------------------------------------ > > Key: SWSQE-453 > URL: https://issues.jboss.org/browse/SWSQE-453 > Project: Kiali QE > Issue Type: QE Task > Reporter: Hayk Hovsepyan > Assignee: Michael Foley > Priority: Blocker > > Currently if there is Kiali pod in Terminating state, and a new Kiali pod running, the checker job loops on the terminating one and timeout. > It should ignore this pod and verify only the running one. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-453) Checker job - Skip Terminating Kiali

by Hayk Hovsepyan (Jira)

Hayk Hovsepyan created SWSQE-453: ------------------------------------ Summary: Checker job - Skip Terminating Kiali Key: SWSQE-453 URL: https://issues.jboss.org/browse/SWSQE-453 Project: Kiali QE Issue Type: QE Task Reporter: Hayk Hovsepyan Assignee: Michael Foley Currently if there is Kiali pod in Terminating state, and a new Kiali pod running, the checker job loops on the terminating one and timeout. It should ignore this pod and verify only the running one. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira October 2018