June 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-2662) Guided Rule Editor does not open popup when binding a variable of type java.time.LocalDate in another constraint

by Jozef Marko (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2662?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-2662: -------------------------------- Sprint: 2018 Week 25-26 > Guided Rule Editor does not open popup when binding a variable of type java.time.LocalDate in another constraint > ---------------------------------------------------------------------------------------------------------------- > > Key: DROOLS-2662 > URL: https://issues.jboss.org/browse/DROOLS-2662 > Project: Drools > Issue Type: Bug > Components: Guided Rule Editor > Reporter: Jozef Marko > Assignee: Jozef Marko > Attachments: out-15.ogv > > > Consider a Data Object Test with a single field date of type java.time.LocalDate. When using Guided Rule Editor with two different conditions on Test object, with two Test object (the condition are in two separated objects), when we bind the date to a variable the constraint pop up won't open for the other condition, showing an error in console. > The attached video will clarify the issue. > That does not seem to happen with built in types and not even with java.util.Date type. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2660) Duplicated variable names in different scopes breaks executable model generation

by Kris Verlaenen (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2660?page=com.atlassian.jira.plugi... ] Kris Verlaenen updated DROOLS-2660: ----------------------------------- Sprint: 2018 Week 25-26 (was: RHPAM7-Iteration14) > Duplicated variable names in different scopes breaks executable model generation > -------------------------------------------------------------------------------- > > Key: DROOLS-2660 > URL: https://issues.jboss.org/browse/DROOLS-2660 > Project: Drools > Issue Type: Bug > Components: core engine > Reporter: Mario Fusco > Assignee: Mario Fusco > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2625) Executable model - AccumulateTest and other tests fail with the model

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2625?page=com.atlassian.jira.plugi... ] Mario Fusco commented on DROOLS-2625: ------------------------------------- All fixes up to the 8th have been already backported to 7.7.x branch. > Executable model - AccumulateTest and other tests fail with the model > --------------------------------------------------------------------- > > Key: DROOLS-2625 > URL: https://issues.jboss.org/browse/DROOLS-2625 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 7.7.0.Final > Reporter: Tibor Zimányi > Assignee: Mario Fusco > > Tests from these test classes from drools-compiler module fail (350 out of 1014 cases) with the executable model: > - AccumulateTest > - AlphaNetworkModifyTest > - AlphaTest > - AnnotationsTest > - ArrayTest > - BackwardChainingTest > PR with tests: https://github.com/kiegroup/drools/pull/1941 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-322) istio upstream installation is not working on b18

by Filip Brychta (JIRA)

[ https://issues.jboss.org/browse/SWSQE-322?page=com.atlassian.jira.plugin.... ] Filip Brychta commented on SWSQE-322: ------------------------------------- "Make sure you use 'oc login' with a user that is an admin before running the playbook" was resolved by adding cluster-admin role to user1 in a way which works with istio installer - https://github.com/openshift/origin/issues/19703 However there is still following problem which is not related to b18: cp: cannot stat '/home/jenkins/.istio/istio-0.8.0/install/kubernetes/istio.yaml': No such file or directory" It's caused by this https://github.com/istio/istio/pull/6144 which is already merged to master but there is no istio release containing that fix. The latest is still 0.8.0 without the fix. I created https://issues.jboss.org/browse/SWSQE-323 to track that. > istio upstream installation is not working on b18 > ------------------------------------------------- > > Key: SWSQE-322 > URL: https://issues.jboss.org/browse/SWSQE-322 > Project: Kiali QE > Issue Type: Task > Reporter: Filip Brychta > Assignee: Filip Brychta > > Installation is failing with "msg": "Make sure you use 'oc login' with a user that is an admin before running the playbook" -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-322) istio upstream installation is not working on b18

by Filip Brychta (JIRA)

[ https://issues.jboss.org/browse/SWSQE-322?page=com.atlassian.jira.plugin.... ] Filip Brychta resolved SWSQE-322. --------------------------------- Resolution: Done > istio upstream installation is not working on b18 > ------------------------------------------------- > > Key: SWSQE-322 > URL: https://issues.jboss.org/browse/SWSQE-322 > Project: Kiali QE > Issue Type: Task > Reporter: Filip Brychta > Assignee: Filip Brychta > > Installation is failing with "msg": "Make sure you use 'oc login' with a user that is an admin before running the playbook" -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-323) Update ansible/istioctl jenkins slave when new istio version is available

by Filip Brychta (JIRA)

Filip Brychta created SWSQE-323: ----------------------------------- Summary: Update ansible/istioctl jenkins slave when new istio version is available Key: SWSQE-323 URL: https://issues.jboss.org/browse/SWSQE-323 Project: Kiali QE Issue Type: Task Reporter: Filip Brychta Assignee: Filip Brychta The latest istio release is currently https://github.com/istio/istio/releases/tag/0.8.0 which does not contain fix in https://github.com/istio/istio/pull/6144 so installation is failing. When there is new release containing the fix we need to rebuild jenkins slave image to contain the fix. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2156) DMN decision table names should be presented as titles in editor screen.

by Jozef Marko (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2156?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-2156: -------------------------------- Description: To help the user identify which table they are working on the name of the table should be presented in the editor view, as a page/table title. h3. Manual Acceptance Test Define multiple decision nodes, each holding different expression type as root entry - Check the heading is updated by clicking in navigation dock (/) - Check the heading is updated by navigating manually by using back to (/) - Check the heading is updated in the expression type is changed (/) - Check the heading is not affected when decision node is renamed (/) was: To help the user identify which table they are working on the name of the table should be presented in the editor view, as a page/table title. h3. Manual Acceptance Test Define multiple decision nodes, each holding different expression type as root entry - Check the heading is updated by clicking in navigation dock (/) - Check the heading is updated by navigating manually by using back to (/) - Check the heading is updated in the expression type is changed (/) - Check the heading is not affected when decision node is renamed (x) > DMN decision table names should be presented as titles in editor screen. > ------------------------------------------------------------------------ > > Key: DROOLS-2156 > URL: https://issues.jboss.org/browse/DROOLS-2156 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Reporter: Liz Clayton > Assignee: Michael Anstis > Labels: UX > Attachments: DROOLS-2156 (success).mp4, rename-error.webm > > > To help the user identify which table they are working on the name of the table should be presented in the editor view, as a page/table title. > h3. Manual Acceptance Test > Define multiple decision nodes, each holding different expression type as root entry > - Check the heading is updated by clicking in navigation dock (/) > - Check the heading is updated by navigating manually by using back to (/) > - Check the heading is updated in the expression type is changed (/) > - Check the heading is not affected when decision node is renamed (/) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-322) istio upstream installation is not working on b18

by Filip Brychta (JIRA)

Filip Brychta created SWSQE-322: ----------------------------------- Summary: istio upstream installation is not working on b18 Key: SWSQE-322 URL: https://issues.jboss.org/browse/SWSQE-322 Project: Kiali QE Issue Type: Task Reporter: Filip Brychta Assignee: Filip Brychta Installation is failing with "msg": "Make sure you use 'oc login' with a user that is an admin before running the playbook" -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-321) Istio Downstream Installer: Add Istio Auth

by Hayk Hovsepyan (JIRA)

[ https://issues.jboss.org/browse/SWSQE-321?page=com.atlassian.jira.plugin.... ] Hayk Hovsepyan updated SWSQE-321: --------------------------------- Team: Infrastructure (was: Jupiter) > Istio Downstream Installer: Add Istio Auth > ------------------------------------------ > > Key: SWSQE-321 > URL: https://issues.jboss.org/browse/SWSQE-321 > Project: Kiali QE > Issue Type: QE Task > Reporter: Hayk Hovsepyan > Assignee: Hayk Hovsepyan > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-321) Istio Downstream Installer: Add Istio Auth

by Hayk Hovsepyan (JIRA)

Hayk Hovsepyan created SWSQE-321: ------------------------------------ Summary: Istio Downstream Installer: Add Istio Auth Key: SWSQE-321 URL: https://issues.jboss.org/browse/SWSQE-321 Project: Kiali QE Issue Type: QE Task Reporter: Hayk Hovsepyan Assignee: Hayk Hovsepyan -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 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 2018