July 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-5484) DMN test DT in context reports warn of no matched rules

by Kris Verlaenen (Jira)

[ https://issues.redhat.com/browse/DROOLS-5484?page=com.atlassian.jira.plug... ] Kris Verlaenen updated DROOLS-5484: ----------------------------------- Sprint: 2020 Week 25-27 (from Jun 15), 2020 Week 28-30 (from Jul 6) (was: 2020 Week 25-27 (from Jun 15)) > DMN test DT in context reports warn of no matched rules > ------------------------------------------------------- > > Key: DROOLS-5484 > URL: https://issues.redhat.com/browse/DROOLS-5484 > Project: Drools > Issue Type: Task > Components: dmn engine > Reporter: Matteo Mortari > Assignee: Matteo Mortari > Priority: Major > > follows up on > https://github.com/kiegroup/drools/commit/01e8ff9d9a38e3232d532c879b24a8a... > and > https://github.com/kiegroup/drools/commit/49be6c816880f64262eb0cdb08bcb59... > to make sure the WARN of no matched rules also applies when the DT is in context (entries and result) -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5458) Running tests should not affect incremental build

by Kris Verlaenen (Jira)

[ https://issues.redhat.com/browse/DROOLS-5458?page=com.atlassian.jira.plug... ] Kris Verlaenen updated DROOLS-5458: ----------------------------------- Sprint: 2020 Week 25-27 (from Jun 15), 2020 Week 28-30 (from Jul 6) (was: 2020 Week 25-27 (from Jun 15)) > Running tests should not affect incremental build > ------------------------------------------------- > > Key: DROOLS-5458 > URL: https://issues.redhat.com/browse/DROOLS-5458 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Affects Versions: 7.39.0.Final > Reporter: Jan Stastny > Assignee: Toni Rikkola > Priority: Blocker > Labels: drools-tools > Attachments: bpms_scesim-tickets.zip > > > For a Scenario Simulation that tests DRL rule and facts having an enum property a seemingly class-loading issue occurs in Business Central. > The ultimate error is in the DRL file validation: > {code:java|title=DRL file} > package org.jboss.qa.ba.scesim; > rule "child ticket" > when > t: Ticket ( type==TicketType.CHILD) > then > t.setPrice(5.0); > end > {code} > {code:java|title=Validation error} > [KBase: defaultKieBase]: Unable to Analyse Expression type == TicketType.CHILD: > [Error: Comparison operation requires compatible types. Found class org.jboss.qa.ba.scesim.TicketType and class org.jboss.qa.ba.scesim.TicketType] > [Near : {... type == TicketType.CHILD ....}] > ^ > {code} > The issue happens in given scenario: > # import project > # go to DRL file and run validation - succeeds > # go to scenario simulation and run - succeeds > # go back to DRL file and run validation - fails with the error above > # go to scenario simulation and run again - fails due to the rule not being evaluated for given facts > The issue disappears when running Build of the project in the Project perspective. > -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5457) XLS Decision table: File indexed before content is saved

by Kris Verlaenen (Jira)

[ https://issues.redhat.com/browse/DROOLS-5457?page=com.atlassian.jira.plug... ] Kris Verlaenen updated DROOLS-5457: ----------------------------------- Sprint: 2020 Week 25-27 (from Jun 15), 2020 Week 28-30 (from Jul 6) (was: 2020 Week 25-27 (from Jun 15)) > XLS Decision table: File indexed before content is saved > -------------------------------------------------------- > > Key: DROOLS-5457 > URL: https://issues.redhat.com/browse/DROOLS-5457 > Project: Drools > Issue Type: Bug > Components: XLS Decision Table Editor > Reporter: Toni Rikkola > Assignee: Toni Rikkola > Priority: Major > Labels: drools-tools > Attachments: Screenshot from 2020-06-30 08-59-18.png, demo.xls, oom-error.log > > > The upload first creates an empty file and then streams the content into the file. These is a gap where indexing can start before content is in place. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5389) Create single abstract class for integration tests in new PMML implementation

by Kris Verlaenen (Jira)

[ https://issues.redhat.com/browse/DROOLS-5389?page=com.atlassian.jira.plug... ] Kris Verlaenen updated DROOLS-5389: ----------------------------------- Sprint: 2020 Week 22-24 (from May 25), 2020 Week 25-27 (from Jun 15), 2020 Week 28-30 (from Jul 6) (was: 2020 Week 22-24 (from May 25), 2020 Week 25-27 (from Jun 15)) > Create single abstract class for integration tests in new PMML implementation > ----------------------------------------------------------------------------- > > Key: DROOLS-5389 > URL: https://issues.redhat.com/browse/DROOLS-5389 > Project: Drools > Issue Type: Task > Reporter: Jiri Petrlik > Assignee: Jiri Petrlik > Priority: Major > Labels: TrustyAI > > Currently there are multiple abstract classes for PMML integration tests such as AbstractPMMLTreeTest, AbstractPMMLRegressionTest etc. The goal of this JIRA is to unify them and create one single abstract class. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4582) Cell selection doesn't span the entire cell if you Insert RightMost Column

by Kris Verlaenen (Jira)

[ https://issues.redhat.com/browse/DROOLS-4582?page=com.atlassian.jira.plug... ] Kris Verlaenen updated DROOLS-4582: ----------------------------------- Sprint: 2020 Week 25-27 (from Jun 15), 2020 Week 28-30 (from Jul 6) (was: 2020 Week 25-27 (from Jun 15)) > Cell selection doesn't span the entire cell if you Insert RightMost Column > -------------------------------------------------------------------------- > > Key: DROOLS-4582 > URL: https://issues.redhat.com/browse/DROOLS-4582 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Reporter: Anna Dupliak > Assignee: Yeser Amer > Priority: Minor > Labels: CustomerFocus, drools-tools > Attachments: image-2019-10-01-10-50-42-411.png, span.webm > > > !image-2019-10-01-10-50-42-411.png|thumbnail! > Selection doesn't span entirely if you bind new column -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5329) Review externalizing lambda failure case

by Kris Verlaenen (Jira)

[ https://issues.redhat.com/browse/DROOLS-5329?page=com.atlassian.jira.plug... ] Kris Verlaenen updated DROOLS-5329: ----------------------------------- Sprint: 2020 Week 19-21 (from May 4), 2020 Week 22-24 (from May 25), 2020 Week 25-27 (from Jun 15), 2020 Week 28-30 (from Jul 6) (was: 2020 Week 19-21 (from May 4), 2020 Week 22-24 (from May 25), 2020 Week 25-27 (from Jun 15)) > Review externalizing lambda failure case > ---------------------------------------- > > Key: DROOLS-5329 > URL: https://issues.redhat.com/browse/DROOLS-5329 > Project: Drools > Issue Type: Task > Components: executable model > Affects Versions: 7.37.0.Final > Reporter: Toshiya Kobayashi > Assignee: Toshiya Kobayashi > Priority: Major > > In CompilerTest#testStringValueOf, there is a case where MaterializedLambdaPredicate is not created. > {code:java} > public static org.drools.model.Rule rule_R() { > final org.drools.model.Variable<java.lang.Integer> var_GENERATED_$pattern_Integer$1$ = D.declarationOf(java.lang.Integer.class, > DomainClassesMetadata81A66AD685F7689036AAA5128956C14B.java_lang_Integer_Metadata_INSTANCE, > "GENERATED_$pattern_Integer$1$"); > final org.drools.model.Variable<Integer> var_$i = D.declarationOf(Integer.class, "$i"); > final org.drools.model.Variable<org.drools.modelcompiler.domain.Person> var_GENERATED_$pattern_Person$1$ = D.declarationOf(org.drools.modelcompiler.domain.Person.class, > DomainClassesMetadata81A66AD685F7689036AAA5128956C14B.org_drools_modelcompiler_domain_Person_Metadata_INSTANCE, > "GENERATED_$pattern_Person$1$"); > org.drools.model.Rule rule = D.rule("R").build(D.pattern(var_GENERATED_$pattern_Integer$1$).bind(var_$i, (java.lang.Integer _this) -> _this.intValue()), > D.pattern(var_GENERATED_$pattern_Person$1$).expr("476633DA7C4638FC84A32859E0C843E6", > var_$i, > (_this, $i) -> org.drools.modelcompiler.util.EvaluationUtil.areNullSafeEquals(_this.getName(), > (String.valueOf($i))), > D.reactOn("name")), > D.on(var_$i).execute(defaultpkg.P1D.LambdaConsequence1D5F4C5CA006007B1D3974ED5A5A05B6.INSTANCE)); > return rule; > } > {code} > See > {code:java} > expr("476633DA7C4638FC84A32859E0C843E6", > var_$i, > (_this, $i) -> org.drools.modelcompiler.util.EvaluationUtil.areNullSafeEquals(_this.getName(), > (String.valueOf($i))) > {code} > It throws DoNotConvertLambdaException in ExecModelLambdaPostProcessor. > {code:java} > private void extractLambdaFromMethodCall(MethodCallExpr methodCallExpr, Supplier<MaterializedLambda> lambdaExtractor) { > methodCallExpr.getArguments().forEach(a -> { > if (a.isLambdaExpr()) { > LambdaExpr lambdaExpr = a.asLambdaExpr(); > try { > CreatedClass aClass = lambdaExtractor.get().create(lambdaExpr.toString(), imports, staticImports); > lambdaClasses.put(aClass.getClassNameWithPackage(), aClass); > ClassOrInterfaceType type = StaticJavaParser.parseClassOrInterfaceType(aClass.getClassNameWithPackage()); > a.replace(lambdaInstance(type)); > } catch(DoNotConvertLambdaException e) { > logger.debug("Cannot externalize lambdas {}", e.getMessage()); > } > } > }); > } > {code} > Review if it's something can be fixed. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5072) DMN investigate wire DT static analysis to kie-maven-plugin

by Kris Verlaenen (Jira)

[ https://issues.redhat.com/browse/DROOLS-5072?page=com.atlassian.jira.plug... ] Kris Verlaenen updated DROOLS-5072: ----------------------------------- Sprint: 2020 Week 16-18 (from Apr 13), 2020 Week 22-24 (from May 25), 2020 Week 25-27 (from Jun 15), 2020 Week 28-30 (from Jul 6) (was: 2020 Week 16-18 (from Apr 13), 2020 Week 22-24 (from May 25), 2020 Week 25-27 (from Jun 15)) > DMN investigate wire DT static analysis to kie-maven-plugin > ----------------------------------------------------------- > > Key: DROOLS-5072 > URL: https://issues.redhat.com/browse/DROOLS-5072 > Project: Drools > Issue Type: Feature Request > Components: dmn engine > Reporter: Matteo Mortari > Assignee: Matteo Mortari > Priority: Major > > followup [DROOLS-5020] -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5232) Improve DMNDI validation rule

by Kris Verlaenen (Jira)

[ https://issues.redhat.com/browse/DROOLS-5232?page=com.atlassian.jira.plug... ] Kris Verlaenen updated DROOLS-5232: ----------------------------------- Sprint: 2020 Week 16-18 (from Apr 13), 2020 Week 19-21 (from May 4), 2020 Week 22-24 (from May 25), 2020 Week 25-27 (from Jun 15), 2020 Week 28-30 (from Jul 6) (was: 2020 Week 16-18 (from Apr 13), 2020 Week 19-21 (from May 4), 2020 Week 22-24 (from May 25), 2020 Week 25-27 (from Jun 15)) > Improve DMNDI validation rule > ----------------------------- > > Key: DROOLS-5232 > URL: https://issues.redhat.com/browse/DROOLS-5232 > Project: Drools > Issue Type: Enhancement > Components: dmn engine > Reporter: Toshiya Kobayashi > Assignee: Toshiya Kobayashi > Priority: Minor > > Improve DMNDI validation rule not to use eval function. > Idea: Add a static java function which takes Definitions and will produce as output all descendant children. So we can write a rule to get them by single "from". > https://github.com/kiegroup/drools/pull/2839#discussion_r405998284 -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5282) Client side FEEL

by Kris Verlaenen (Jira)

[ https://issues.redhat.com/browse/DROOLS-5282?page=com.atlassian.jira.plug... ] Kris Verlaenen updated DROOLS-5282: ----------------------------------- Sprint: 2020 Week 16-18 (from Apr 13), 2020 Week 19-21 (from May 4), 2020 Week 22-24 (from May 25), 2020 Week 25-27 (from Jun 15), 2020 Week 28-30 (from Jul 6) (was: 2020 Week 16-18 (from Apr 13), 2020 Week 19-21 (from May 4), 2020 Week 22-24 (from May 25), 2020 Week 25-27 (from Jun 15)) > Client side FEEL > ---------------- > > Key: DROOLS-5282 > URL: https://issues.redhat.com/browse/DROOLS-5282 > Project: Drools > Issue Type: Epic > Reporter: Toni Rikkola > Assignee: Toni Rikkola > Priority: Major > Labels: drools-tools > > Make kie-dmn-feel usable in the client side. > Notes: > * FEEL functions use reflection, but many if not all of them can be hard coded -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5262) java.lang.Number import remains in the list of imports after deletion

by Kris Verlaenen (Jira)

[ https://issues.redhat.com/browse/DROOLS-5262?page=com.atlassian.jira.plug... ] Kris Verlaenen updated DROOLS-5262: ----------------------------------- Sprint: 2020 Week 16-18 (from Apr 13), 2020 Week 19-21 (from May 4), 2020 Week 22-24 (from May 25), 2020 Week 25-27 (from Jun 15), 2020 Week 28-30 (from Jul 6) (was: 2020 Week 16-18 (from Apr 13), 2020 Week 19-21 (from May 4), 2020 Week 22-24 (from May 25), 2020 Week 25-27 (from Jun 15)) > java.lang.Number import remains in the list of imports after deletion > --------------------------------------------------------------------- > > Key: DROOLS-5262 > URL: https://issues.redhat.com/browse/DROOLS-5262 > Project: Drools > Issue Type: Bug > Affects Versions: 7.37.0.Final > Reporter: Jozef Marko > Assignee: Jozef Marko > Priority: Optional > Labels: drools-tools > Attachments: Screenshot from 2018-01-09 12-56-56.png > > > When you delete java.lang.Number from project's imports in the business central and you create some asset in this project, java.lang.Number is still present in External imports of the created asset. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 2 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira July 2020