December 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-3417) Fix neverending loop on ScenarioSimulationGridHeaderUtilitiesTest

by Gabriele Cardosi (Jira)

Gabriele Cardosi created DROOLS-3417: ---------------------------------------- Summary: Fix neverending loop on ScenarioSimulationGridHeaderUtilitiesTest Key: DROOLS-3417 URL: https://issues.jboss.org/browse/DROOLS-3417 Project: Drools Issue Type: Bug Reporter: Gabriele Cardosi Assignee: Gabriele Cardosi After merging of https://github.com/kiegroup/appformer/pull/556, testGetUiHeaderRowIndexRow0() and testGetUiHeaderRowIndexRow1() methods enter an endless loop. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2333) Automatic addition of join condition properties to property reactive watch doesn't work when the first pattern doesn't have any constraint

by Mario Fusco (Jira)

[ https://issues.jboss.org/browse/DROOLS-2333?page=com.atlassian.jira.plugi... ] Mario Fusco resolved DROOLS-2333. --------------------------------- Resolution: Done > Automatic addition of join condition properties to property reactive watch doesn't work when the first pattern doesn't have any constraint > ------------------------------------------------------------------------------------------------------------------------------------------ > > Key: DROOLS-2333 > URL: https://issues.jboss.org/browse/DROOLS-2333 > Project: Drools > Issue Type: Bug > Components: core engine > Reporter: Mario Fusco > Assignee: Mario Fusco > Priority: Major > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3416) Allow Drools (executable model) to be compiled on Graal

by Mario Fusco (Jira)

Mario Fusco created DROOLS-3416: ----------------------------------- Summary: Allow Drools (executable model) to be compiled on Graal Key: DROOLS-3416 URL: https://issues.jboss.org/browse/DROOLS-3416 Project: Drools Issue Type: Task Reporter: Mario Fusco Assignee: Mario Fusco -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3415) guided decision tree updation is not hapening

by Mario Fusco (Jira)

[ https://issues.jboss.org/browse/DROOLS-3415?page=com.atlassian.jira.plugi... ] Mario Fusco reassigned DROOLS-3415: ----------------------------------- Assignee: Toni Rikkola (was: Mario Fusco) > guided decision tree updation is not hapening > --------------------------------------------- > > Key: DROOLS-3415 > URL: https://issues.jboss.org/browse/DROOLS-3415 > Project: Drools > Issue Type: Bug > Reporter: Shankar Prasad > Assignee: Toni Rikkola > Priority: Major > Attachments: Screenshot 2018-12-07 at 9.42.13 AM.png, Screenshot 2018-12-07 at 9.42.25 AM.png, Screenshot 2018-12-07 at 9.42.37 AM.png > > > I have a guided decision tree where I am trying to update a ENUM field but once I click OK on the workbench, it is taking the default value. I am using KIE workbench 7.12.0. > I have given complete screenshot and details in > https://groups.google.com/forum/#!topic/drools-usage/xjVBBtyPbdc -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3234) Add a Donut widget to improve the visualisation of test report screen

by Toni Rikkola (Jira)

[ https://issues.jboss.org/browse/DROOLS-3234?page=com.atlassian.jira.plugi... ] Toni Rikkola commented on DROOLS-3234: -------------------------------------- [~kkufova] We can merge, but there might still be some changes that need to be done. I'm not 100% sure I have everything setup so that the UI just fits the needs, but I can make another PR for the additional changes. > Add a Donut widget to improve the visualisation of test report screen > --------------------------------------------------------------------- > > Key: DROOLS-3234 > URL: https://issues.jboss.org/browse/DROOLS-3234 > Project: Drools > Issue Type: Enhancement > Components: Scenario Simulation and Testing, Test Scenarios Editor > Reporter: Toni Rikkola > Assignee: Toni Rikkola > Priority: Major > Attachments: donut.png, pie2b.png, screencast-04-12-18.webm > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3415) guided decision tree updation is not hapening

by Shankar Prasad (Jira)

Shankar Prasad created DROOLS-3415: -------------------------------------- Summary: guided decision tree updation is not hapening Key: DROOLS-3415 URL: https://issues.jboss.org/browse/DROOLS-3415 Project: Drools Issue Type: Bug Reporter: Shankar Prasad Assignee: Mario Fusco Attachments: Screenshot 2018-12-07 at 9.42.13 AM.png, Screenshot 2018-12-07 at 9.42.25 AM.png, Screenshot 2018-12-07 at 9.42.37 AM.png I have a guided decision tree where I am trying to update a ENUM field but once I click OK on the workbench, it is taking the default value. I am using KIE workbench 7.12.0. I have given complete screenshot and details in https://groups.google.com/forum/#!topic/drools-usage/xjVBBtyPbdc -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3415) guided decision tree updation is not hapening

by Shankar Prasad (Jira)

[ https://issues.jboss.org/browse/DROOLS-3415?page=com.atlassian.jira.plugi... ] Shankar Prasad updated DROOLS-3415: ----------------------------------- Attachment: Screenshot 2018-12-07 at 9.42.25 AM.png Screenshot 2018-12-07 at 9.42.37 AM.png Screenshot 2018-12-07 at 9.42.13 AM.png > guided decision tree updation is not hapening > --------------------------------------------- > > Key: DROOLS-3415 > URL: https://issues.jboss.org/browse/DROOLS-3415 > Project: Drools > Issue Type: Bug > Reporter: Shankar Prasad > Assignee: Mario Fusco > Priority: Major > Attachments: Screenshot 2018-12-07 at 9.42.13 AM.png, Screenshot 2018-12-07 at 9.42.25 AM.png, Screenshot 2018-12-07 at 9.42.37 AM.png > > > I have a guided decision tree where I am trying to update a ENUM field but once I click OK on the workbench, it is taking the default value. I am using KIE workbench 7.12.0. > I have given complete screenshot and details in > https://groups.google.com/forum/#!topic/drools-usage/xjVBBtyPbdc -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11384) StatefulFailoverTestCase fails intermittently

by Ondrej Kotek (Jira)

[ https://issues.jboss.org/browse/WFLY-11384?page=com.atlassian.jira.plugin... ] Ondrej Kotek commented on WFLY-11384: ------------------------------------- Seems OK, thank you. > StatefulFailoverTestCase fails intermittently > --------------------------------------------- > > Key: WFLY-11384 > URL: https://issues.jboss.org/browse/WFLY-11384 > Project: WildFly > Issue Type: Bug > Components: Clustering, Test Suite > Affects Versions: 15.0.0.Beta1 > Environment: Any > Reporter: Ondrej Kotek > Assignee: Radoslav Husar > Priority: Major > Fix For: 16.0.0.Beta1 > > > The tests of {{org.jboss.as.test.clustering.cluster.ejb.stateful.StatefulFailoverTestCase}} occasionally fail, for example: > {noformat} > [ERROR] Failures: > [ERROR] StatefulFailoverTestCase.jmsConnectionFactoryFailover:166->failover:193->queryCount:315 expected:<200> but was:<500> > [ERROR] StatefulFailoverTestCase.nestedBeanFailover:286->queryCount:315 expected:<200> but was:<500> > [ERROR] StatefulFailoverTestCase.noFailover:117 expected:<1> but was:<3> > {noformat} > or > {noformat} > [ERROR] Failures: > [ERROR] StatefulFailoverTestCase.nestedBeanFailover:286->queryCount:315 expected:<200> but was:<500> > [ERROR] StatefulFailoverTestCase.noFailover:117->queryCount:315 expected:<200> but was:<500> > [ERROR] StatefulFailoverTestCase.simpleFailover:145->failover:193->queryCount:315 expected:<200> but was:<500> > {noformat} > connectionFactoryFailover: https://ci.wildfly.org/project.html?projectId=WF&testNameId=-822829635945... > noFailover: https://ci.wildfly.org/project.html?projectId=WF&testNameId=-574944609062... > jmsConnectionFactoryFailover: https://ci.wildfly.org/project.html?projectId=WF&testNameId=3564603678560... > simpleFailover: https://ci.wildfly.org/project.html?projectId=WF&testNameId=4824753507849... -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4234) WARN if jboss-deployment-structure.xml excludes non-existent dependency

by Chao Wang (Jira)

[ https://issues.jboss.org/browse/WFCORE-4234?page=com.atlassian.jira.plugi... ] Chao Wang reassigned WFCORE-4234: --------------------------------- Assignee: Chao Wang (was: Jason Greene) > WARN if jboss-deployment-structure.xml excludes non-existent dependency > ----------------------------------------------------------------------- > > Key: WFCORE-4234 > URL: https://issues.jboss.org/browse/WFCORE-4234 > Project: WildFly Core > Issue Type: Enhancement > Components: Server > Affects Versions: 6.0.2.Final > Reporter: Brad Maxwell > Assignee: Chao Wang > Priority: Major > > WARN if jboss-deployment-structure.xml excludes non-existent dependency > Users can be off by a character or list a dependency that does not exist. A warning would let them know that their configuration has an issue. > {code} > <?xml version="1.0" encoding="UTF-8" ?> > <jboss-deployment-structure xmlns="urn:jboss:deployment-structure:1.2"> > <ear-subdeployments-isolated>false</ear-subdeployments-isolated> > <deployment> > <exclusions> > <module name="non-existent" /> > </exclusions> > </deployment> > </jboss-deployment-structure> > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (LOGMGR-228) Reintroduce a way to configure a LogContext via properties

by James Perkins (Jira)

[ https://issues.jboss.org/browse/LOGMGR-228?page=com.atlassian.jira.plugin... ] James Perkins updated LOGMGR-228: --------------------------------- Git Pull Request: https://github.com/jboss-logging/jboss-logmanager/pull/219 > Reintroduce a way to configure a LogContext via properties > ---------------------------------------------------------- > > Key: LOGMGR-228 > URL: https://issues.jboss.org/browse/LOGMGR-228 > Project: JBoss Log Manager > Issue Type: Task > Components: ext > Reporter: James Perkins > Assignee: James Perkins > Priority: Major > > The configuration API was removed and therefore the old way of configuring a {{LogContext}} based on properties. A way to read a properties file and configure a {{LogContext}} based on those properties. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 5 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 December 2018