October 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (SWSQE-468) Istio Upstream Pipeline Changes - Kiali is going be installed by default on Istio 1.1.0

by Guilherme Baufaker Rêgo (Jira)

[ https://issues.jboss.org/browse/SWSQE-468?page=com.atlassian.jira.plugin.... ] Guilherme Baufaker Rêgo reassigned SWSQE-468: --------------------------------------------- Assignee: Guilherme Baufaker Rêgo > Istio Upstream Pipeline Changes - Kiali is going be installed by default on Istio 1.1.0 > --------------------------------------------------------------------------------------- > > Key: SWSQE-468 > URL: https://issues.jboss.org/browse/SWSQE-468 > Project: Kiali QE > Issue Type: Story > Reporter: Guilherme Baufaker Rêgo > Assignee: Guilherme Baufaker Rêgo > Priority: Major > > - When this new Istio 1.1.0 comes, Kiali is going to be part of the "default" installation, which means our pipeline will need to remove this kiali and reinstall other from PR. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-469) Jenkins Slave for Complex Meshes

by Guilherme Baufaker Rêgo (Jira)

[ https://issues.jboss.org/browse/SWSQE-469?page=com.atlassian.jira.plugin.... ] Guilherme Baufaker Rêgo resolved SWSQE-469. ------------------------------------------- Resolution: Done > Jenkins Slave for Complex Meshes > -------------------------------- > > Key: SWSQE-469 > URL: https://issues.jboss.org/browse/SWSQE-469 > Project: Kiali QE > Issue Type: Task > Reporter: Guilherme Baufaker Rêgo > Assignee: Guilherme Baufaker Rêgo > Priority: Major > > Complex Mesh would need to have it is own Jenkins Slave -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11225) The 'local provider builder' dependencies from org.wildfly.transactions.client module should be made optional

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFLY-11225?page=com.atlassian.jira.plugin... ] Brian Stansberry commented on WFLY-11225: ----------------------------------------- Grepping the wildfly-transaction-client code base for the packages provided by the org.jboss.jboss-transaction-spi, org.jboss.jts and org.jboss.jts.integration modules confirms that the only uses are from JBossLocalTransactionProvider and its subclasses, which are only used if the transaction subsystem (LocalTransactionContextService) uses them. So no transaction subsystem means no use, and hence the deps are optional. {code} $ git grep org.jboss.tm src/main/java/org/wildfly/transaction/client/provider/jboss/JBossJTALocalTransactionProvider.java:import org.jboss.tm.ExtendedJBossXATerminator; src/main/java/org/wildfly/transaction/client/provider/jboss/JBossJTALocalTransactionProvider.java:import org.jboss.tm.TransactionTimeoutConfiguration; src/main/java/org/wildfly/transaction/client/provider/jboss/JBossJTALocalTransactionProvider.java:import org.jboss.tm.XAResourceRecoveryRegistry; src/main/java/org/wildfly/transaction/client/provider/jboss/JBossJTSLocalTransactionProvider.java:import org.jboss.tm.ExtendedJBossXATerminator; src/main/java/org/wildfly/transaction/client/provider/jboss/JBossJTSLocalTransactionProvider.java:import org.jboss.tm.TransactionTimeoutConfiguration; src/main/java/org/wildfly/transaction/client/provider/jboss/JBossJTSLocalTransactionProvider.java:import org.jboss.tm.XAResourceRecoveryRegistry; src/main/java/org/wildfly/transaction/client/provider/jboss/JBossLocalTransactionProvider.java:import org.jboss.tm.ExtendedJBossXATerminator; src/main/java/org/wildfly/transaction/client/provider/jboss/JBossLocalTransactionProvider.java:import org.jboss.tm.ImportedTransaction; src/main/java/org/wildfly/transaction/client/provider/jboss/JBossLocalTransactionProvider.java:import org.jboss.tm.TransactionImportResult; src/main/java/org/wildfly/transaction/client/provider/jboss/JBossLocalTransactionProvider.java:import org.jboss.tm.XAResourceRecoveryRegistry; $ git grep com.arjuna src/main/java/org/wildfly/transaction/client/provider/jboss/JBossJTALocalTransactionProvider.java:import com.arjuna.ats.internal.jta.resources.arjunacore.SynchronizationImple; src/main/java/org/wildfly/transaction/client/provider/jboss/JBossJTALocalTransactionProvider.java:import com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple; src/main/java/org/wildfly/transaction/client/provider/jboss/JBossJTALocalTransactionProvider.java:import com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionManagerImple; src/main/java/org/wildfly/transaction/client/provider/jboss/JBossJTSLocalTransactionProvider.java:import com.arjuna.ats.internal.jta.resources.jts.orbspecific.JTAInterposedSynchronizationImple; src/main/java/org/wildfly/transaction/client/provider/jboss/JBossJTSLocalTransactionProvider.java:import com.arjuna.ats.internal.jta.resources.jts.orbspecific.SynchronizationImple; src/main/java/org/wildfly/transaction/client/provider/jboss/JBossJTSLocalTransactionProvider.java:import com.arjuna.ats.internal.jta.transaction.jts.TransactionImple; src/main/java/org/wildfly/transaction/client/provider/jboss/JBossJTSLocalTransactionProvider.java:import com.arjuna.ats.internal.jta.transaction.jts.TransactionManagerImple; src/main/java/org/wildfly/transaction/client/provider/jboss/JBossLocalTransactionProvider.java:import static com.arjuna.ats.arjuna.coordinator.TwoPhaseOutcome.INVALID_TRANSACTION; src/main/java/org/wildfly/transaction/client/provider/jboss/JBossLocalTransactionProvider.java:import static com.arjuna.ats.arjuna.coordinator.TwoPhaseOutcome.PREPARE_NOTOK; src/main/java/org/wildfly/transaction/client/provider/jboss/JBossLocalTransactionProvider.java:import static com.arjuna.ats.arjuna.coordinator.TwoPhaseOutcome.PREPARE_OK; src/main/java/org/wildfly/transaction/client/provider/jboss/JBossLocalTransactionProvider.java:import static com.arjuna.ats.arjuna.coordinator.TwoPhaseOutcome.PREPARE_READONLY; src/main/java/org/wildfly/transaction/client/provider/jboss/JBossLocalTransactionProvider.java:import com.arjuna.ats.arjuna.common.arjPropertyManager; src/main/java/org/wildfly/transaction/client/provider/jboss/JBossLocalTransactionProvider.java: if (transactionManager instanceof com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionManagerImple src/main/java/org/wildfly/transaction/client/provider/jboss/JBossLocalTransactionProvider.java: || transactionManager instanceof com.arjuna.ats.jbossatx.jta.TransactionManagerDelegate) { src/main/java/org/wildfly/transaction/client/provider/jboss/JBossLocalTransactionProvider.java: } else if (transactionManager instanceof com.arjuna.ats.internal.jta.transaction.jts.TransactionManagerImple src/main/java/org/wildfly/transaction/client/provider/jboss/JBossLocalTransactionProvider.java: || transactionManager instanceof com.arjuna.ats.jbossatx.jts.TransactionManagerDelegate) { $ git grep org.omg $ git grep org.jboss.narayana pom.xml: <version.org.jboss.narayana>5.5.30.Final</version.org.jboss.narayana> pom.xml: <groupId>org.jboss.narayana.jts</groupId> pom.xml: <version>${version.org.jboss.narayana}</version> pom.xml: <groupId>org.jboss.narayana.jts</groupId> pom.xml: <version>${version.org.jboss.narayana}</version> pom.xml: <groupId>org.jboss.narayana.jta</groupId> pom.xml: <version>${version.org.jboss.narayana}</version> {code} > The 'local provider builder' dependencies from org.wildfly.transactions.client module should be made optional > ------------------------------------------------------------------------------------------------------------- > > Key: WFLY-11225 > URL: https://issues.jboss.org/browse/WFLY-11225 > Project: WildFly > Issue Type: Enhancement > Components: Transactions > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Priority: Major > > The org.wildfly.transactions.client module includes some non-optional dependencies that appear to only be required if JBossLocalTransactionProvider.builder() is used by outside code that provides a local transaction provider. AKA the transaction subsystem. This means those dependencies are optional in cases where there is no such caller. > The outside caller (i.e. the transaction subsystem module) can ensure that a non-optional dependency on the required modules exists. > This change will allow other modules that have a classloading dependency on org.wildfly.transactions.client but don't necessarily care whether a local tx provider is actually installed to depend on the module without forcing inclusion of these dependencies. > Features provided by modules that depend on org.wildfly.transactions.client and that also require that a local tx provider be installed should create a management model requirement for a capability. See WFLY-11166. > See also discussion at http://post-office.corp.redhat.com/archives/eap-pm-list/2018-October/msg0... -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11225) The 'local provider builder' dependencies from org.wildfly.transactions.client module should be made optional

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFLY-11225?page=com.atlassian.jira.plugin... ] Brian Stansberry reassigned WFLY-11225: --------------------------------------- Assignee: Brian Stansberry (was: Tom Jenkinson) > The 'local provider builder' dependencies from org.wildfly.transactions.client module should be made optional > ------------------------------------------------------------------------------------------------------------- > > Key: WFLY-11225 > URL: https://issues.jboss.org/browse/WFLY-11225 > Project: WildFly > Issue Type: Enhancement > Components: Transactions > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Priority: Major > > The org.wildfly.transactions.client module includes some non-optional dependencies that appear to only be required if JBossLocalTransactionProvider.builder() is used by outside code that provides a local transaction provider. AKA the transaction subsystem. This means those dependencies are optional in cases where there is no such caller. > The outside caller (i.e. the transaction subsystem module) can ensure that a non-optional dependency on the required modules exists. > This change will allow other modules that have a classloading dependency on org.wildfly.transactions.client but don't necessarily care whether a local tx provider is actually installed to depend on the module without forcing inclusion of these dependencies. > Features provided by modules that depend on org.wildfly.transactions.client and that also require that a local tx provider be installed should create a management model requirement for a capability. See WFLY-11166. > See also discussion at http://post-office.corp.redhat.com/archives/eap-pm-list/2018-October/msg0... -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2552) KieBase Deserialization: NullPointerException

by Florian Braun (Jira)

[ https://issues.jboss.org/browse/DROOLS-2552?page=com.atlassian.jira.plugi... ] Florian Braun updated DROOLS-2552: ---------------------------------- Priority: Critical (was: Major) > KieBase Deserialization: NullPointerException > --------------------------------------------- > > Key: DROOLS-2552 > URL: https://issues.jboss.org/browse/DROOLS-2552 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 7.7.0.Final > Environment: Windows 7, Java 1.8, Drools 7.7.0.Final, jBPM 7.7.0.Final > Reporter: Florian Braun > Assignee: Mario Fusco > Priority: Critical > > I have run into an issue with the KieBase serialization throwing a NullPointerException when using exists and parentheses around an or when rules are in a RuleFlowGroup. > Example rules: > package com.sample.rules > rule "Your First Rule" > ruleflow-group "group1" > when > exists ( String(this == "Hello") or String(this == "World") ) > then > System.out.println("Hello or World"); > end > rule "Your Second Rule" > ruleflow-group "group1" > when > $string: String(this == "Hello World") > then > System.out.println($string); > end > Having the first rule wrap the or in () will cause a deserialization NPE: > Exception in thread "main" java.lang.NullPointerException > at org.drools.core.common.BaseNode.getSinks(BaseNode.java:241) > at org.drools.core.impl.KnowledgeBaseImpl.rewireNodeAfterDeserialization(KnowledgeBaseImpl.java:494) > at org.drools.core.impl.KnowledgeBaseImpl.rewireNodeAfterDeserialization(KnowledgeBaseImpl.java:511) > at org.drools.core.impl.KnowledgeBaseImpl.rewireNodeAfterDeserialization(KnowledgeBaseImpl.java:511) > at org.drools.core.impl.KnowledgeBaseImpl.rewireNodeAfterDeserialization(KnowledgeBaseImpl.java:511) > at org.drools.core.impl.KnowledgeBaseImpl.rewireReteAfterDeserialization(KnowledgeBaseImpl.java:489) > at org.drools.core.impl.KnowledgeBaseImpl.readExternal(KnowledgeBaseImpl.java:483) > .... > Some testing shows this: > If the first rule is on its own then this error does *not* occur. > If the first rule does not use () the error does *not* occur. This of course means that the rule behaves differently > If the rules are not in an rfg this error does *not* occur -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3111) [DMN Designer] Decision table generation fails if custom input data connected

by Michael Anstis (Jira)

[ https://issues.jboss.org/browse/DROOLS-3111?page=com.atlassian.jira.plugi... ] Michael Anstis updated DROOLS-3111: ----------------------------------- Sprint: 2018 Week 42-44 > [DMN Designer] Decision table generation fails if custom input data connected > ----------------------------------------------------------------------------- > > Key: DROOLS-3111 > URL: https://issues.jboss.org/browse/DROOLS-3111 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.13.0.Final > Reporter: Jozef Marko > Assignee: Michael Anstis > Priority: Major > Labels: drools-tools > Attachments: a1.dmn, aaa.dmn > > > The decision table generation according to connected input data nodes fails if some custom input data is connected. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3111) [DMN Designer] Decision table generation fails if custom input data connected

by Michael Anstis (Jira)

[ https://issues.jboss.org/browse/DROOLS-3111?page=com.atlassian.jira.plugi... ] Michael Anstis updated DROOLS-3111: ----------------------------------- Story Points: 3 > [DMN Designer] Decision table generation fails if custom input data connected > ----------------------------------------------------------------------------- > > Key: DROOLS-3111 > URL: https://issues.jboss.org/browse/DROOLS-3111 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.13.0.Final > Reporter: Jozef Marko > Assignee: Michael Anstis > Priority: Major > Labels: drools-tools > Attachments: a1.dmn, aaa.dmn > > > The decision table generation according to connected input data nodes fails if some custom input data is connected. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3111) [DMN Designer] Decision table generation fails if custom input data connected

by Daniel José dos Santos (Jira)

[ https://issues.jboss.org/browse/DROOLS-3111?page=com.atlassian.jira.plugi... ] Daniel José dos Santos reassigned DROOLS-3111: ---------------------------------------------- Assignee: Michael Anstis (was: Daniel José dos Santos) > [DMN Designer] Decision table generation fails if custom input data connected > ----------------------------------------------------------------------------- > > Key: DROOLS-3111 > URL: https://issues.jboss.org/browse/DROOLS-3111 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.13.0.Final > Reporter: Jozef Marko > Assignee: Michael Anstis > Priority: Major > Labels: drools-tools > Attachments: a1.dmn, aaa.dmn > > > The decision table generation according to connected input data nodes fails if some custom input data is connected. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3203) [DMN Designer] Runtime issues

by Michael Anstis (Jira)

[ https://issues.jboss.org/browse/DROOLS-3203?page=com.atlassian.jira.plugi... ] Michael Anstis updated DROOLS-3203: ----------------------------------- Priority: Blocker (was: Major) > [DMN Designer] Runtime issues > ----------------------------- > > Key: DROOLS-3203 > URL: https://issues.jboss.org/browse/DROOLS-3203 > Project: Drools > Issue Type: Epic > Components: DMN Editor > Reporter: Michael Anstis > Assignee: Michael Anstis > Priority: Blocker > > An umbrella for the issues we're encountering with _using_ DMN models authored with _our_ editor. A lot of issues are being reported as comments on PRs or as separate JIRA. In reality, in preparation for our MVP we need to be confident all such issues are captured, fixed and re-tested. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3203) [DMN Designer] Runtime issues

by Michael Anstis (Jira)

[ https://issues.jboss.org/browse/DROOLS-3203?page=com.atlassian.jira.plugi... ] Michael Anstis updated DROOLS-3203: ----------------------------------- Tester: Jozef Marko Story Points: 13 Sprint: 2018 Week 42-44 > [DMN Designer] Runtime issues > ----------------------------- > > Key: DROOLS-3203 > URL: https://issues.jboss.org/browse/DROOLS-3203 > Project: Drools > Issue Type: Epic > Components: DMN Editor > Reporter: Michael Anstis > Assignee: Michael Anstis > Priority: Major > > An umbrella for the issues we're encountering with _using_ DMN models authored with _our_ editor. A lot of issues are being reported as comments on PRs or as separate JIRA. In reality, in preparation for our MVP we need to be confident all such issues are captured, fixed and re-tested. -- 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