August 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JGRP-2498) Move dependent projects to 5.0

by Bela Ban (Jira)

[ https://issues.redhat.com/browse/JGRP-2498?page=com.atlassian.jira.plugin... ] Bela Ban edited comment on JGRP-2498 at 8/17/20 7:36 AM: --------------------------------------------------------- Done (changed and released): * jgroups-kubernetes: 2.0.0.Final * native-s3-ping: released 1.0.0.Final (4.x) and 2.0.0.Final (5.0.1) * jgroups-netty: Beta4 (5.0.1) * jgroups-google: released 1.0.0.Final (4.x) and 2.0.0.Final (5.0.1) * jgroups-azure: released 2.0.0.Final (5.0.1) * gossiprouter-image: lastest now uses 5.0.1, 1.0 uses 4.2.5 was (Author: belaban): Done (changed and released): * jgroups-kubernetes: 2.0.0.Final * native-s3-ping: released 1.0.0.Final (4.x) and 2.0.0.Final (5.0.1) * jgroups-netty: Beta4 (5.0.1) * jgroups-google: released 1.0.0.Final (4.x) and 2.0.0.Final (5.0.1) * jgroups-azure: released 2.0.0.Final (5.0.1) > Move dependent projects to 5.0 > ------------------------------ > > Key: JGRP-2498 > URL: https://issues.redhat.com/browse/JGRP-2498 > Project: JGroups > Issue Type: Task > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Major > Fix For: 5.0.2 > > > Move projects that consume JGroups (e.g. in jgroups-extras) to 5.0. The {{master}} branch would use 5.0, and the newly created (old) branch 4.x. > The projects are under [https://github.com/jgroups-extras|http://example.com] -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-1205) Automate Joined Configs Section https://github.com/kiali/kiali-ui/pull/1885

by Hayk Hovsepyan (Jira)

[ https://issues.redhat.com/browse/SWSQE-1205?page=com.atlassian.jira.plugi... ] Hayk Hovsepyan reassigned SWSQE-1205: ------------------------------------- Assignee: Hayk Hovsepyan > Automate Joined Configs Section https://github.com/kiali/kiali-ui/pull/1885 > --------------------------------------------------------------------------- > > Key: SWSQE-1205 > URL: https://issues.redhat.com/browse/SWSQE-1205 > Project: Kiali QE > Issue Type: QE Task > Reporter: Hayk Hovsepyan > Assignee: Hayk Hovsepyan > Priority: Major > Labels: automation > -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5576) Unable to further edit scesim header cell when editing mode previously canceled with Esc

by Kris Verlaenen (Jira)

[ https://issues.redhat.com/browse/DROOLS-5576?page=com.atlassian.jira.plug... ] Kris Verlaenen updated DROOLS-5576: ----------------------------------- Sprint: 2020 Week 31-33 (from Jul 27), 2020 Week 34-36 (from Aug 17) (was: 2020 Week 31-33 (from Jul 27)) > Unable to further edit scesim header cell when editing mode previously canceled with Esc > ---------------------------------------------------------------------------------------- > > Key: DROOLS-5576 > URL: https://issues.redhat.com/browse/DROOLS-5576 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Affects Versions: 7.42.0.Final > Reporter: Jan Stastny > Assignee: Jozef Marko > Priority: Major > > In Rule based Test Scenario an alias in Given/Expect facts for either instance or property can be introduced (i.e. in header cells) and override the default instance/property names. > The header cell can be opened in editing mode by either double-clicking on it or arrow key navigation and pressing Enter. > When the editing mode is opened the changes can be either confirmed (by pressing Enter or Tab) or canceled (by pressing Esc). > When the editing mode is canceled using Esc, any consecutive attempt to edit that exact cell is not successful - the editing mode for the cell can't be opened neither by clicking nor pressing any keys. > For others (not yet hit by the issue) the editing mode opens fine up to the moment described above. > The issue is not present in ordinary cells (the lines for actual test scenario definitions below the header cells of the grid.) > The only workaround is to close and open the editor anew. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5575) Review dtanalysis DMN examples version in codebase

by Kris Verlaenen (Jira)

[ https://issues.redhat.com/browse/DROOLS-5575?page=com.atlassian.jira.plug... ] Kris Verlaenen updated DROOLS-5575: ----------------------------------- Sprint: 2020 Week 31-33 (from Jul 27), 2020 Week 34-36 (from Aug 17) (was: 2020 Week 31-33 (from Jul 27)) > Review dtanalysis DMN examples version in codebase > -------------------------------------------------- > > Key: DROOLS-5575 > URL: https://issues.redhat.com/browse/DROOLS-5575 > Project: Drools > Issue Type: Task > Components: dmn engine > Reporter: Matteo Mortari > Assignee: Matteo Mortari > Priority: Major > -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5570) Share kie-dmn-versionconverter

by Kris Verlaenen (Jira)

[ https://issues.redhat.com/browse/DROOLS-5570?page=com.atlassian.jira.plug... ] Kris Verlaenen updated DROOLS-5570: ----------------------------------- Sprint: 2020 Week 31-33 (from Jul 27), 2020 Week 34-36 (from Aug 17) (was: 2020 Week 31-33 (from Jul 27)) > Share kie-dmn-versionconverter > ------------------------------ > > Key: DROOLS-5570 > URL: https://issues.redhat.com/browse/DROOLS-5570 > Project: Drools > Issue Type: Task > Components: dmn engine > Reporter: Matteo Mortari > Assignee: Matteo Mortari > Priority: Major > -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4606) DMN alpha network POC

by Kris Verlaenen (Jira)

[ https://issues.redhat.com/browse/DROOLS-4606?page=com.atlassian.jira.plug... ] Kris Verlaenen updated DROOLS-4606: ----------------------------------- Sprint: 2019 Week 41-43 (from Okt 7), 2019 Week 44-46 (from Okt 28), 2019 Week 47-49 (from Nov 18), 2020 Week 31-33 (from Jul 27), 2020 Week 34-36 (from Aug 17) (was: 2019 Week 41-43 (from Okt 7), 2019 Week 44-46 (from Okt 28), 2019 Week 47-49 (from Nov 18), 2020 Week 31-33 (from Jul 27)) > DMN alpha network POC > --------------------- > > Key: DROOLS-4606 > URL: https://issues.redhat.com/browse/DROOLS-4606 > Project: Drools > Issue Type: Task > Components: dmn engine > Reporter: Matteo Mortari > Assignee: Luca Molteni > Priority: Major > > Start refactoring work to support alpha network -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5557) kie-dmn-validation migration to exec model

by Kris Verlaenen (Jira)

[ https://issues.redhat.com/browse/DROOLS-5557?page=com.atlassian.jira.plug... ] Kris Verlaenen updated DROOLS-5557: ----------------------------------- Sprint: 2020 Week 31-33 (from Jul 27), 2020 Week 34-36 (from Aug 17) (was: 2020 Week 31-33 (from Jul 27)) > kie-dmn-validation migration to exec model > ------------------------------------------ > > Key: DROOLS-5557 > URL: https://issues.redhat.com/browse/DROOLS-5557 > Project: Drools > Issue Type: Story > Components: dmn engine > Reporter: Matteo Mortari > Assignee: Matteo Mortari > Priority: Major > > kie-dmn-validation migration to exec model -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5517) Enhance DMNResult/DMNContext to be able to return strongly typed OutputSet

by Kris Verlaenen (Jira)

[ https://issues.redhat.com/browse/DROOLS-5517?page=com.atlassian.jira.plug... ] Kris Verlaenen updated DROOLS-5517: ----------------------------------- Sprint: 2020 Week 31-33 (from Jul 27), 2020 Week 34-36 (from Aug 17) (was: 2020 Week 31-33 (from Jul 27)) > Enhance DMNResult/DMNContext to be able to return strongly typed OutputSet > -------------------------------------------------------------------------- > > Key: DROOLS-5517 > URL: https://issues.redhat.com/browse/DROOLS-5517 > Project: Drools > Issue Type: Enhancement > Components: dmn engine > Affects Versions: 7.40.0.Final > Reporter: Toshiya Kobayashi > Assignee: Toshiya Kobayashi > Priority: Major > > DROOLS-5502 was to generate OutputSet class and convert DMNResult.getContext().getAll() to the OutputSet externally. This JIRA aims to convert it inside DMNRuntime so that we can get the OutputSet from DMNResult.getContext().getXXX() directly. > https://github.com/kiegroup/drools/pull/2993#pullrequestreview-451150317 -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5486) CEP doesn't evaluate correctly when a bind variable is used as the first temporal parameter in executable model

by Kris Verlaenen (Jira)

[ https://issues.redhat.com/browse/DROOLS-5486?page=com.atlassian.jira.plug... ] Kris Verlaenen updated DROOLS-5486: ----------------------------------- Sprint: 2020 Week 28-30 (from Jul 6), 2020 Week 31-33 (from Jul 27), 2020 Week 34-36 (from Aug 17) (was: 2020 Week 28-30 (from Jul 6), 2020 Week 31-33 (from Jul 27)) > CEP doesn't evaluate correctly when a bind variable is used as the first temporal parameter in executable model > --------------------------------------------------------------------------------------------------------------- > > Key: DROOLS-5486 > URL: https://issues.redhat.com/browse/DROOLS-5486 > Project: Drools > Issue Type: Bug > Components: executable model > Affects Versions: 7.39.0.Final > Reporter: Toshiya Kobayashi > Assignee: Toshiya Kobayashi > Priority: Major > > With the below test, standard-drl fires but executable-model doesn't. > {code:java} > @Test > public void testAfterOnLongFields2() throws Exception { > String str = > "import " + StockTick.class.getCanonicalName() + ";\n" + > "declare StockTick @timestamp(timeFieldAsLong) end\n" + > "rule R when\n" + > " $a : StockTick( company == \"DROO\" )\n" + > " $b : StockTick( company == \"ACME\", $a.timeFieldAsLong after[5,8] timeFieldAsLong )\n" + > "then\n" + > " System.out.println(\"fired\");\n" + > "end\n"; > KieSession ksession = getKieSession(getCepKieModuleModel(), str); > SessionPseudoClock clock = ksession.getSessionClock(); > > ReteDumper.dumpRete(ksession); > ksession.insert( new StockTick( "ACME" ).setTimeField( 0 ) ); > ksession.insert( new StockTick( "DROO" ).setTimeField( 6 ) ); > assertEquals( 1, ksession.fireAllRules() ); > } > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5378) Alpha Node ordering

by Kris Verlaenen (Jira)

[ https://issues.redhat.com/browse/DROOLS-5378?page=com.atlassian.jira.plug... ] Kris Verlaenen updated DROOLS-5378: ----------------------------------- Sprint: 2020 Week 25-27 (from Jun 15), 2020 Week 28-30 (from Jul 6), 2020 Week 31-33 (from Jul 27), 2020 Week 34-36 (from Aug 17) (was: 2020 Week 25-27 (from Jun 15), 2020 Week 28-30 (from Jul 6), 2020 Week 31-33 (from Jul 27)) > Alpha Node ordering > ------------------- > > Key: DROOLS-5378 > URL: https://issues.redhat.com/browse/DROOLS-5378 > Project: Drools > Issue Type: Enhancement > Components: core engine > Affects Versions: 7.38.0.Final > Reporter: Toshiya Kobayashi > Assignee: Toshiya Kobayashi > Priority: Major > > Re-order Alpha Node based on some strategies: > - Expression usage count > - Other strategies : Chapter 9 "Ordering Conditions" in http://i.stanford.edu/pub/cstr/reports/cs/tr/86/1124/CS-TR-86-1124.pdf > It would contribute to maximise sharing and minimise the number of evaluations. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 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 August 2020