October 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-4641) Running the Traffic Violation tutorial closing DMN editor Zoom toolbar persisted

by Matteo Mortari (Jira)

Matteo Mortari created DROOLS-4641: -------------------------------------- Summary: Running the Traffic Violation tutorial closing DMN editor Zoom toolbar persisted Key: DROOLS-4641 URL: https://issues.jboss.org/browse/DROOLS-4641 Project: Drools Issue Type: Bug Components: Stunner Reporter: Matteo Mortari Assignee: Mario Fusco Attachments: image-2019-10-11-11-16-50-339.png As per title. Following the Traffic Violation tutorial. Closing the DMN editor. the Zoom bar persist on screen as per screenshot. !image-2019-10-11-11-16-50-339.png|thumbnail! Not sure this is the correct JIRA component, please move this JIRA as necessary -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4641) Running the Traffic Violation tutorial closing DMN editor Zoom toolbar persisted

by Matteo Mortari (Jira)

[ https://issues.jboss.org/browse/DROOLS-4641?page=com.atlassian.jira.plugi... ] Matteo Mortari reassigned DROOLS-4641: -------------------------------------- Assignee: Michael Anstis (was: Mario Fusco) > Running the Traffic Violation tutorial closing DMN editor Zoom toolbar persisted > -------------------------------------------------------------------------------- > > Key: DROOLS-4641 > URL: https://issues.jboss.org/browse/DROOLS-4641 > Project: Drools > Issue Type: Bug > Components: Stunner > Reporter: Matteo Mortari > Assignee: Michael Anstis > Priority: Major > Attachments: image-2019-10-11-11-16-50-339.png > > > As per title. Following the Traffic Violation tutorial. Closing the DMN editor. the Zoom bar persist on screen as per screenshot. > !image-2019-10-11-11-16-50-339.png|thumbnail! > Not sure this is the correct JIRA component, please move this JIRA as necessary -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4640) DMN Editor constraint on Type does not reflect in Decision Table

by Matteo Mortari (Jira)

[ https://issues.jboss.org/browse/DROOLS-4640?page=com.atlassian.jira.plugi... ] Matteo Mortari updated DROOLS-4640: ----------------------------------- Description: Editing the classic Traffic Violation item definition to put enumeration on string for the violation type "speed", "parking", ... once done in the item definition is not reflected in the decision table, and that prevents also from getting the real intended DT static analysis message for the table. !image-2019-10-11-11-02-31-881.png|thumbnail! in the attached screenshot I entered the data also manually in the DT's property right tab. was: Editing the classic Traffic Violation item definition to put enumeration on string for the violation type "speed", "parking", ... once done in the item definition is not reflected in the decision table, and that prevents also from getting the real intended DT static analysis message for the table. !image-2019-10-11-11-02-31-881.png|thumbnail! > DMN Editor constraint on Type does not reflect in Decision Table > ---------------------------------------------------------------- > > Key: DROOLS-4640 > URL: https://issues.jboss.org/browse/DROOLS-4640 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Reporter: Matteo Mortari > Assignee: Guilherme Gomes > Priority: Major > Attachments: image-2019-10-11-11-02-31-881.png > > > Editing the classic Traffic Violation item definition to put enumeration on string for the violation type "speed", "parking", ... once done in the item definition is not reflected in the decision table, and that prevents also from getting the real intended DT static analysis message for the table. > !image-2019-10-11-11-02-31-881.png|thumbnail! > in the attached screenshot I entered the data also manually in the DT's property right tab. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4640) DMN Editor constraint on Type does not reflect in Decision Table

by Matteo Mortari (Jira)

[ https://issues.jboss.org/browse/DROOLS-4640?page=com.atlassian.jira.plugi... ] Matteo Mortari updated DROOLS-4640: ----------------------------------- Description: Editing the classic Traffic Violation item definition to put enumeration on string for the violation type "speed", "parking", ... once done in the item definition is not reflected in the decision table, and that prevents also from getting the real intended DT static analysis message for the table. !image-2019-10-11-11-02-31-881.png|thumbnail! was: Editing the classic Traffic Violation item definition to put enumeration on string for the violation type "speed", "parking", ... once done in the item definition is not reflected in the decision table, and that prevents from getting the real intended DT static analysis message for the table. !image-2019-10-11-11-02-31-881.png|thumbnail! > DMN Editor constraint on Type does not reflect in Decision Table > ---------------------------------------------------------------- > > Key: DROOLS-4640 > URL: https://issues.jboss.org/browse/DROOLS-4640 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Reporter: Matteo Mortari > Assignee: Guilherme Gomes > Priority: Major > Attachments: image-2019-10-11-11-02-31-881.png > > > Editing the classic Traffic Violation item definition to put enumeration on string for the violation type "speed", "parking", ... once done in the item definition is not reflected in the decision table, and that prevents also from getting the real intended DT static analysis message for the table. > !image-2019-10-11-11-02-31-881.png|thumbnail! -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4640) DMN Editor constraint on Type does not reflect in Decision Table

by Matteo Mortari (Jira)

Matteo Mortari created DROOLS-4640: -------------------------------------- Summary: DMN Editor constraint on Type does not reflect in Decision Table Key: DROOLS-4640 URL: https://issues.jboss.org/browse/DROOLS-4640 Project: Drools Issue Type: Enhancement Components: DMN Editor Reporter: Matteo Mortari Assignee: Guilherme Gomes Attachments: image-2019-10-11-11-02-31-881.png Editing the classic Traffic Violation item definition to put enumeration on string for the violation type "speed", "parking", ... once done in the item definition is not reflected in the decision table, and that prevents from getting the real intended DT static analysis message for the table. !image-2019-10-11-11-02-31-881.png|thumbnail! -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12657) KUBE_PING too frequent warning metadata.labels.pod-template-hash not found in pod json. Impossible to reliably determine pod group during Rolling Update

by Jeff Mesnil (Jira)

[ https://issues.jboss.org/browse/WFLY-12657?page=com.atlassian.jira.plugin... ] Jeff Mesnil commented on WFLY-12657: ------------------------------------ Tracked in https://github.com/jgroups-extras/jgroups-kubernetes/issues/75 > KUBE_PING too frequent warning metadata.labels.pod-template-hash not found in pod json. Impossible to reliably determine pod group during Rolling Update > -------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-12657 > URL: https://issues.jboss.org/browse/WFLY-12657 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 18.0.0.Final > Reporter: Martin Simka > Assignee: Radoslav Husar > Priority: Major > > In my test application on openshift KUBE_PING logs warning every 20-30s . > {noformat} > 13:27:05,340 WARN [org.jgroups.protocols.kubernetes.KUBE_PING] (thread-51,ee,tx-server-0) metadata.labels.pod-template-hash not found in pod json. Impossible to reliably determine pod group during Rolling Update > 13:27:40,600 WARN [org.jgroups.protocols.kubernetes.KUBE_PING] (thread-52,ee,tx-server-0) metadata.labels.pod-template-hash not found in pod json. Impossible to reliably determine pod group during Rolling Update > 13:27:40,600 WARN [org.jgroups.protocols.kubernetes.KUBE_PING] (thread-52,ee,tx-server-0) metadata.labels.pod-template-hash not found in pod json. Impossible to reliably determine pod group during Rolling Update > 13:27:57,892 WARN [org.jgroups.protocols.kubernetes.KUBE_PING] (thread-52,ee,tx-server-0) metadata.labels.pod-template-hash not found in pod json. Impossible to reliably determine pod group during Rolling Update > 13:27:57,892 WARN [org.jgroups.protocols.kubernetes.KUBE_PING] (thread-52,ee,tx-server-0) metadata.labels.pod-template-hash not found in pod json. Impossible to reliably determine pod group during Rolling Update > 13:28:21,104 WARN [org.jgroups.protocols.kubernetes.KUBE_PING] (thread-51,ee,tx-server-0) metadata.labels.pod-template-hash not found in pod json. Impossible to reliably determine pod group during Rolling Update > 13:28:21,104 WARN [org.jgroups.protocols.kubernetes.KUBE_PING] (thread-51,ee,tx-server-0) metadata.labels.pod-template-hash not found in pod json. Impossible to reliably determine pod group during Rolling Update > 13:28:45,737 WARN [org.jgroups.protocols.kubernetes.KUBE_PING] (thread-52,ee,tx-server-0) metadata.labels.pod-template-hash not found in pod json. Impossible to reliably determine pod group during Rolling Update > 13:28:45,737 WARN [org.jgroups.protocols.kubernetes.KUBE_PING] (thread-52,ee,tx-server-0) metadata.labels.pod-template-hash not found in pod json. Impossible to reliably determine pod group during Rolling Update > 13:29:05,335 WARN [org.jgroups.protocols.kubernetes.KUBE_PING] (thread-51,ee,tx-server-0) metadata.labels.pod-template-hash not found in pod json. Impossible to reliably determine pod group during Rolling Update > 13:29:05,335 WARN [org.jgroups.protocols.kubernetes.KUBE_PING] (thread-51,ee,tx-server-0) metadata.labels.pod-template-hash not found in pod json. Impossible to reliably determine pod group during Rolling Update > 13:29:29,027 WARN [org.jgroups.protocols.kubernetes.KUBE_PING] (thread-51,ee,tx-server-0) metadata.labels.pod-template-hash not found in pod json. Impossible to reliably determine pod group during Rolling Update > 13:29:29,027 WARN [org.jgroups.protocols.kubernetes.KUBE_PING] (thread-51,ee,tx-server-0) metadata.labels.pod-template-hash not found in pod json. Impossible to reliably determine pod group during Rolling Update > 13:30:04,195 WARN [org.jgroups.protocols.kubernetes.KUBE_PING] (thread-51,ee,tx-server-0) metadata.labels.pod-template-hash not found in pod json. Impossible to reliably determine pod group during Rolling Update > 13:30:04,195 WARN [org.jgroups.protocols.kubernetes.KUBE_PING] (thread-51,ee,tx-server-0) metadata.labels.pod-template-hash not found in pod json. Impossible to reliably determine pod group during Rolling Update > {noformat} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4708) Upgrade XNIO to 3.7.6.Final

by Jeff Mesnil (Jira)

Jeff Mesnil created WFCORE-4708: ----------------------------------- Summary: Upgrade XNIO to 3.7.6.Final Key: WFCORE-4708 URL: https://issues.jboss.org/browse/WFCORE-4708 Project: WildFly Core Issue Type: Component Upgrade Components: Server Reporter: Ivo Studensky Assignee: Jeff Mesnil Fix For: 11.0.0.Beta1 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12662) Update BouncyCastle

by Rostislav Svoboda (Jira)

Rostislav Svoboda created WFLY-12662: ---------------------------------------- Summary: Update BouncyCastle Key: WFLY-12662 URL: https://issues.jboss.org/browse/WFLY-12662 Project: WildFly Issue Type: Task Reporter: Rostislav Svoboda Assignee: Rostislav Svoboda Update BouncyCastle -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-976) Prepare downstream pipeline for UI tests

by Filip Brychta (Jira)

Filip Brychta created SWSQE-976: ----------------------------------- Summary: Prepare downstream pipeline for UI tests Key: SWSQE-976 URL: https://issues.jboss.org/browse/SWSQE-976 Project: Kiali QE Issue Type: QE Task Reporter: Filip Brychta Assignee: Filip Brychta UI tests need just one control plane and two bookinfo apps currently. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12601) Eliminate StabilityMonitor usages in clustering subsystem

by Richard Opalka (Jira)

[ https://issues.jboss.org/browse/WFLY-12601?page=com.atlassian.jira.plugin... ] Richard Opalka commented on WFLY-12601: --------------------------------------- I just finished the review [~pferraro], you did excellent job! > Eliminate StabilityMonitor usages in clustering subsystem > --------------------------------------------------------- > > Key: WFLY-12601 > URL: https://issues.jboss.org/browse/WFLY-12601 > Project: WildFly > Issue Type: Bug > Components: Clustering > Reporter: Richard Opalka > Assignee: Paul Ferraro > Priority: Major > Fix For: 19.0.0.Beta1 > > Attachments: ServiceSupplier.png > > > Clustering needs to eliminate usages of StabilityMonitor because SM is not reliable. > It is possible that SM will prematurely inform about achieved stability even if it is not true. > The reason is SM is not propagated up the dependencies chain and thus it may report > about achieved stability even in case dependencies chain didn't finish its processing yet > and 'real' stability wasn't achieved yet. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 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 2019