June 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-2644) [DMN Designer] Deletion of the column causes last column width increase

by Jozef Marko (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2644?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-2644: -------------------------------- Description: There are situations when the undo of column deletion causes unexpected grid total width increase. See the steps to reproduce. h3. Manual Accpetance Test Steps to reproduce fixed # Decision table # Relation was:There are situations when the undo of column deletion causes unexpected grid total width increase. See the steps to reproduce. > [DMN Designer] Deletion of the column causes last column width increase > ----------------------------------------------------------------------- > > Key: DROOLS-2644 > URL: https://issues.jboss.org/browse/DROOLS-2644 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.8.0.Final > Reporter: Jozef Marko > Assignee: Michael Anstis > Priority: Minor > > There are situations when the undo of column deletion causes unexpected grid total width increase. See the steps to reproduce. > h3. Manual Accpetance Test > Steps to reproduce fixed > # Decision table > # Relation -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-2473) [DMN Designer] Function language change inconsistency

by Jozef Marko (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2473?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-2473: -------------------------------- Description: If the function language is changed, the boxed expression table is not rendered as expected. h2. PR Acceptance Test Change of function language is consistent in rendering - Empty function (/) - Function with data (/) - Function as boxed expression not at top level in the context hierarchy (/) was: If the function language is changed, the boxed expression table is not rendered as expected. h2. PR Acceptance Test Change of function language is consistent in rendering - Empty function - Function with data - Function as boxed expression not at top level in the context hierarchy > [DMN Designer] Function language change inconsistency > ----------------------------------------------------- > > Key: DROOLS-2473 > URL: https://issues.jboss.org/browse/DROOLS-2473 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.8.0.Final > Reporter: Jozef Marko > Assignee: Michael Anstis > Priority: Minor > Attachments: Screenshot from 2018-04-13 09-13-54.png, Screenshot from 2018-04-13 09-14-00.png, Screenshot from 2018-04-13 09-14-14.png > > > If the function language is changed, the boxed expression table is not rendered as expected. > h2. PR Acceptance Test > Change of function language is consistent in rendering > - Empty function (/) > - Function with data (/) > - Function as boxed expression not at top level in the context hierarchy (/) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-2628) [DMN Designer] DataInput toolbox actions

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2628?page=com.atlassian.jira.plugi... ] Michael Anstis updated DROOLS-2628: ----------------------------------- Sprint: 2018 Week 23-24 > [DMN Designer] DataInput toolbox actions > ---------------------------------------- > > Key: DROOLS-2628 > URL: https://issues.jboss.org/browse/DROOLS-2628 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.8.0.Final > Reporter: Jozef Marko > Assignee: Michael Anstis > Attachments: Screenshot from 2018-06-11 15-49-28.png, Screenshot from 2018-06-11 15-53-34.png > > > The Data Input node offers not appropriate actions. In the attached screenshot if you check actions on positions *1* and *2* both offer the *Create DMN Decision* action. Furthermore if you select the action at the position *2* the attached error appears. > h3. Manual PR Acceptance Test > Check all toolbox actions of each node type -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-2565) [DMN Editor] Move showcase webapp to "project" based instead of "standalone"

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2565?page=com.atlassian.jira.plugi... ] Michael Anstis updated DROOLS-2565: ----------------------------------- Sprint: 2018 Week 23-24 > [DMN Editor] Move showcase webapp to "project" based instead of "standalone" > ---------------------------------------------------------------------------- > > Key: DROOLS-2565 > URL: https://issues.jboss.org/browse/DROOLS-2565 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Michael Anstis > Assignee: Michael Anstis > > The DMN standalone showcase webapp does not integrate well into the Workbench as it has a bunch of custom component supporting basic file creation, loading etc. Before we can integrate the DMN Editor into the Workbench (so people can start looking at it) the showcase should be moved to be "project" centric. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (WFLY-10598) Document missing messaging capabilities

by Jeff Mesnil (JIRA)

[ https://issues.jboss.org/browse/WFLY-10598?page=com.atlassian.jira.plugin... ] Jeff Mesnil updated WFLY-10598: ------------------------------- Description: https://github.com/wildfly/wildfly-capabilities/tree/master/org/wildfly/m... https://github.com/wildfly/wildfly-capabilities/tree/master/org/wildfly/m... > Document missing messaging capabilities > --------------------------------------- > > Key: WFLY-10598 > URL: https://issues.jboss.org/browse/WFLY-10598 > Project: WildFly > Issue Type: Sub-task > Components: JMS > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > > https://github.com/wildfly/wildfly-capabilities/tree/master/org/wildfly/m... > https://github.com/wildfly/wildfly-capabilities/tree/master/org/wildfly/m... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (JGRP-2253) FD_SOCK is not working in AWS environment

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-2253?page=com.atlassian.jira.plugin.... ] Bela Ban commented on JGRP-2253: -------------------------------- I can't really see something other than the SUSPECT/UNSUSPECT cycles in your logs, which are suspicious and point to FD_SOCK not being able to connect to the destination it is supposed to monitor: {noformat} 21:52:16.021 TRACE 1108 — [jgroups-13,cluster,ip-143-60500] FD_SOCK : - - ip-143-60500: received SUSPECT message from ip-48-43121: suspects=[ip-143-60500] 21:52:16.022 TRACE 1108 — [jgroups-13,cluster,ip-143-60500] FD_SOCK : - - ip-143-60500: received SUSPECT message from ip-48-43121: suspects=[ip-163-65450] 21:52:16.024 TRACE 1108 — [jgroups-3,cluster,ip-143-60500] FD_SOCK : - - ip-143-60500: received UNSUSPECT message from ip-48-43121: mbrs=[ip-143-60500] 21:52:16.025 TRACE 1108 — [jgroups-4,cluster,ip-143-60500] FD_SOCK : - - ip-143-60500: received UNSUSPECT message from ip-48-43121: mbrs=[ip-163-65450] {noformat} My bet is that this is caused by incorrect ports, which causes FD_SOCK to malfunction. I'm also not sure that termination on EC2/AWS closes the sockets of a process, or whether termination is more like a power-down / pull-the power-plug like behavior. I seem to recall that this was the case. If so, FD_SOCK would not kick in, but FD would instead... > FD_SOCK is not working in AWS environment > ----------------------------------------- > > Key: JGRP-2253 > URL: https://issues.jboss.org/browse/JGRP-2253 > Project: JGroups > Issue Type: Bug > Affects Versions: 4.0.10 > Environment: AWS - EC2 > Reporter: Sibin Karnavar > Assignee: Bela Ban > Fix For: 4.0.13 > > > We have our failure detection defined like below. > <FD_SOCK external_port="7804" /> > <FD timeout="3000" max_tries="3" /> > <VERIFY_SUSPECT timeout="3000" /> > Please note that we have used FD instead of FD_ALL in AWS. We will be changing it to FD_ALL later after detailed testing. > In my local, this is working perfect. As soon as I kill my node, I was able to see that view change was happening immediately with FD_SOCK. > We were not mentioning the external_port in the FD_SOCK but later I thought it may be an issue with the port and defined it as 7804 and added the same port to the security group that allows to access this port among all the nodes. So no issue with the port. > Can you please let us know if we need any additional configurations to make FD_SOCK works well in AWS. > Thanks, > Sibin -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (SWSQE-315) IstioOC fails on B15

by Hayk Hovsepyan (JIRA)

[ https://issues.jboss.org/browse/SWSQE-315?page=com.atlassian.jira.plugin.... ] Hayk Hovsepyan updated SWSQE-315: --------------------------------- Team: Infrastructure > IstioOC fails on B15 > -------------------- > > Key: SWSQE-315 > URL: https://issues.jboss.org/browse/SWSQE-315 > Project: Kiali QE > Issue Type: QE Task > Reporter: Hayk Hovsepyan > Assignee: Hayk Hovsepyan > > OC Cluster is up, but Istio-system project is empty. > http://jenkins2.bc.jonqe.lab.eng.bos.redhat.com:8080/job/IstioOC-cluster-... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (SWSQE-315) IstioOC fails on B15

by Hayk Hovsepyan (JIRA)

Hayk Hovsepyan created SWSQE-315: ------------------------------------ Summary: IstioOC fails on B15 Key: SWSQE-315 URL: https://issues.jboss.org/browse/SWSQE-315 Project: Kiali QE Issue Type: QE Task Reporter: Hayk Hovsepyan Assignee: Hayk Hovsepyan OC Cluster is up, but Istio-system project is empty. http://jenkins2.bc.jonqe.lab.eng.bos.redhat.com:8080/job/IstioOC-cluster-... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (SWSQE-305) B18 is not working after istio-injector was deployed

by Filip Brychta (JIRA)

[ https://issues.jboss.org/browse/SWSQE-305?page=com.atlassian.jira.plugin.... ] Filip Brychta commented on SWSQE-305: ------------------------------------- Reinstalling b18 cluster > B18 is not working after istio-injector was deployed > ---------------------------------------------------- > > Key: SWSQE-305 > URL: https://issues.jboss.org/browse/SWSQE-305 > Project: Kiali QE > Issue Type: QE Task > Reporter: Guilherme Baufaker Rêgo > Assignee: Filip Brychta > Priority: Blocker > > Auto Istio-sidecar-injector was installed on b18 without using the pre-patching as suggested (https://github.com/openshift-istio/openshift-ansible/blob/istio-3.10-0.8....), but it was reverted since it will work only istio 0.8.0+ > now the jobs which install istio resources like kiali-test-mesh are trying to find istio sidecar even though the configuration was removed. > http://jenkins2.bc.jonqe.lab.eng.bos.redhat.com:8080/job/Kiali-Test-Meshe... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (SWSQE-305) B18 is not working after istio-injector was deployed

by Filip Brychta (JIRA)

[ https://issues.jboss.org/browse/SWSQE-305?page=com.atlassian.jira.plugin.... ] Filip Brychta reassigned SWSQE-305: ----------------------------------- Assignee: Filip Brychta (was: Michael Foley) > B18 is not working after istio-injector was deployed > ---------------------------------------------------- > > Key: SWSQE-305 > URL: https://issues.jboss.org/browse/SWSQE-305 > Project: Kiali QE > Issue Type: QE Task > Reporter: Guilherme Baufaker Rêgo > Assignee: Filip Brychta > Priority: Blocker > > Auto Istio-sidecar-injector was installed on b18 without using the pre-patching as suggested (https://github.com/openshift-istio/openshift-ansible/blob/istio-3.10-0.8....), but it was reverted since it will work only istio 0.8.0+ > now the jobs which install istio resources like kiali-test-mesh are trying to find istio sidecar even though the configuration was removed. > http://jenkins2.bc.jonqe.lab.eng.bos.redhat.com:8080/job/Kiali-Test-Meshe... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

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