April 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-5180) Kie-scanner update container API doesn't refresh container with latest jar after new year

by Minal Bhalodi (Jira)

[ https://issues.redhat.com/browse/DROOLS-5180?page=com.atlassian.jira.plug... ] Minal Bhalodi edited comment on DROOLS-5180 at 4/3/20 3:59 PM: --------------------------------------------------------------- I am able to reproduce this problem. 1)First in .m2 folder first I added jar with version name person-10.23.2019-06-30-00.jar and started kie server. Kie-server created container with jar version 10.23.2019-06-30-00. 2)While server was running, I added person-10.23.2019-20-30-00.jar and kie container was updated with latest jar. Though I was adding this jar manually in S3, I also updated maven-metadata-local.xml manually to modify release and version with person-10.23.2019-20-30-00.jar 3)Then again without stopping server, I added person-04.02.2020-15-00-04.jar and updated release and version in maven-metadata-local.xml. This time kie server was not updated with version 04.02.2020-15-00-04. our maven-metadata-local.xml <?xml version="1.0" encoding="UTF-8"?> <metadata> <groupId><value></groupId> <artifactId><value></artifactId> <versioning> <release>10.23.2019-20-30-00</release> <versions> <version>10.23.2019-06-30-00</version> <version>04.02.2020-15-00-04</version> <version>10.23.2019-20-30-00</version> </versions> <lastUpdated>1585869333000</lastUpdated> </versioning> </metadata> I don't have sample code to reproduce this issue but if you can share a sample code where kie-server updates container in reference to .m2 folder then I might be able to reproduce this issue was (Author: mbhalodi_intuit): I am able to reproduce this problem. 1)First in .m2 folder first I added jar with version name person-10.23.2019-06-30-00.jar and started kie server. Kie-server created container with jar version 10.23.2019-06-30-00. 2)While server was running, I added person-10.23.2019-20-30-00.jar and kie container was updated with latest jar. Though I was adding this jar manually in S3, I also updated maven-metadata-local.xml manually to modify release and version with person-10.23.2019-20-30-00.jar 3)Then again without stopping server, I added person-04.02.2020-15-00-04.jar and updated release and version in maven-metadata-local.xml. This time kie server was not updated with version 04.02.2020-15-00-04. our maven-metadata-local.xml <?xml version="1.0" encoding="UTF-8"?> <metadata> <groupId><value></groupId> <artifactId><value></artifactId> <versioning> <release>10.23.2019-20-30-00</release> <versions> <version>10.23.2019-06-30-00</version> <version>04.02.2020-15-00-04</version> <version>10.23.2019-20-30-00</version> </versions> <lastUpdated>1585869333000</lastUpdated> </versioning> </metadata> I don't sample code to reproduce this issue but if you can share a sample code where kie-server updates container in reference to .m2 folder then I might be able to reproudce this issue there > Kie-scanner update container API doesn't refresh container with latest jar after new year > ----------------------------------------------------------------------------------------- > > Key: DROOLS-5180 > URL: https://issues.redhat.com/browse/DROOLS-5180 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 7.18.0.Final > Reporter: Minal Bhalodi > Assignee: Mario Fusco > Priority: Critical > > We are using kie-server as a stand alone application. we use kie scanner to update kie container when there is a new DRL file in our .m2 folder. > we don't have scanner polling but we use Scanner update container API to update kie container. > Every year when date changes after new year, we are facing issue where kie scanner is not able to update container with latest jar in m2 with new year date. > When we check the container version it shows latest with new year date but internally kie is still using old jar. > We fixed this issue with create container API instead update container. > kie-server-spring-boot-starter-drools :7.18.0.Final > Please let me know if this issue is already fixed or discussed before or if you need more details. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5180) Kie-scanner update container API doesn't refresh container with latest jar after new year

by Minal Bhalodi (Jira)

[ https://issues.redhat.com/browse/DROOLS-5180?page=com.atlassian.jira.plug... ] Minal Bhalodi commented on DROOLS-5180: --------------------------------------- Thanks for your help. we were finally able to find the root cause. > Kie-scanner update container API doesn't refresh container with latest jar after new year > ----------------------------------------------------------------------------------------- > > Key: DROOLS-5180 > URL: https://issues.redhat.com/browse/DROOLS-5180 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 7.18.0.Final > Reporter: Minal Bhalodi > Assignee: Mario Fusco > Priority: Critical > > We are using kie-server as a stand alone application. we use kie scanner to update kie container when there is a new DRL file in our .m2 folder. > we don't have scanner polling but we use Scanner update container API to update kie container. > Every year when date changes after new year, we are facing issue where kie scanner is not able to update container with latest jar in m2 with new year date. > When we check the container version it shows latest with new year date but internally kie is still using old jar. > We fixed this issue with create container API instead update container. > kie-server-spring-boot-starter-drools :7.18.0.Final > Please let me know if this issue is already fixed or discussed before or if you need more details. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3580) [DMN Designer] Decision Table: Add support for merged view

by Guilherme Gomes (Jira)

[ https://issues.redhat.com/browse/DROOLS-3580?page=com.atlassian.jira.plug... ] Guilherme Gomes updated DROOLS-3580: ------------------------------------ Sprint: (was: 2020 Week 13-15 (from Mar 23)) > [DMN Designer] Decision Table: Add support for merged view > ---------------------------------------------------------- > > Key: DROOLS-3580 > URL: https://issues.redhat.com/browse/DROOLS-3580 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Affects Versions: 7.17.0.Final > Reporter: Edson Tirelli > Assignee: Guilherme Gomes > Priority: Major > Labels: drools-tools > > Add support for viewing the {{DecisionTableGrid}} in _merged_ mode. > The underlying widget supports merging however I need to check about model synchronisation and where how we'd add a button to toggle merged/unmerged.. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-1110) E2E job - Swagger Version Always 'master'

by Matthew Mahoney (Jira)

[ https://issues.redhat.com/browse/SWSQE-1110?page=com.atlassian.jira.plugi... ] Matthew Mahoney updated SWSQE-1110: ----------------------------------- Comment: was deleted (was: Also please change KIALI_CLIENT default to '0.9.3' https://gitlab.cee.redhat.com/istio/kiali-qe/kiali-qe-jenkins-dsl/blob/ma...) > E2E job - Swagger Version Always 'master' > ----------------------------------------- > > Key: SWSQE-1110 > URL: https://issues.redhat.com/browse/SWSQE-1110 > Project: Kiali QE > Issue Type: Bug > Reporter: Matthew Mahoney > Assignee: Filip Brychta > Priority: Major > Labels: infrastructure > > Issue is that the swagger json is always 'master'. > prepare-e2e-tests-env.sh needs to set the swagger file version/path appropriately based on KIALI_REVISION_SHA1 > https://github.com/kiali/kiali/blob/master/tests/e2e/config/env.yaml#L10 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-1110) E2E job - Swagger Version Always 'master'

by Matthew Mahoney (Jira)

[ https://issues.redhat.com/browse/SWSQE-1110?page=com.atlassian.jira.plugi... ] Matthew Mahoney commented on SWSQE-1110: ---------------------------------------- Also please change the https://gitlab.cee.redhat.com/istio/kiali-qe/kiali-qe-jenkins-dsl/blob/ma... > E2E job - Swagger Version Always 'master' > ----------------------------------------- > > Key: SWSQE-1110 > URL: https://issues.redhat.com/browse/SWSQE-1110 > Project: Kiali QE > Issue Type: Bug > Reporter: Matthew Mahoney > Assignee: Filip Brychta > Priority: Major > Labels: infrastructure > > Issue is that the swagger json is always 'master'. > prepare-e2e-tests-env.sh needs to set the swagger file version/path appropriately based on KIALI_REVISION_SHA1 > https://github.com/kiali/kiali/blob/master/tests/e2e/config/env.yaml#L10 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-1110) E2E job - Swagger Version Always 'master'

by Matthew Mahoney (Jira)

[ https://issues.redhat.com/browse/SWSQE-1110?page=com.atlassian.jira.plugi... ] Matthew Mahoney edited comment on SWSQE-1110 at 4/3/20 3:26 PM: ---------------------------------------------------------------- Also please change KIALI_CLIENT default to '0.9.3' https://gitlab.cee.redhat.com/istio/kiali-qe/kiali-qe-jenkins-dsl/blob/ma... was (Author: mmahoney): Also please change the https://gitlab.cee.redhat.com/istio/kiali-qe/kiali-qe-jenkins-dsl/blob/ma... > E2E job - Swagger Version Always 'master' > ----------------------------------------- > > Key: SWSQE-1110 > URL: https://issues.redhat.com/browse/SWSQE-1110 > Project: Kiali QE > Issue Type: Bug > Reporter: Matthew Mahoney > Assignee: Filip Brychta > Priority: Major > Labels: infrastructure > > Issue is that the swagger json is always 'master'. > prepare-e2e-tests-env.sh needs to set the swagger file version/path appropriately based on KIALI_REVISION_SHA1 > https://github.com/kiali/kiali/blob/master/tests/e2e/config/env.yaml#L10 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4041) ManagementRealm does now show plain-text attribute in default read-resource output

by Michal Petrov (Jira)

[ https://issues.redhat.com/browse/WFCORE-4041?page=com.atlassian.jira.plug... ] Michal Petrov commented on WFCORE-4041: --------------------------------------- [~dlofthouse], [~jdenise] I found out fixing this breaks CLI, specifically "security enable-sasl-management …", as CLI tries to construct the composite operation it performs a lookup for a properties-realm (relying on "plain-text" not being set) - {{ElytronUtil.buildUsersResource()}}. As far as I can see there is no parameter to set the "plain-text" so the CLI operation will currently fail to find a properties-realm with "plain-text=true", I'm assuming that's a bug? > ManagementRealm does now show plain-text attribute in default read-resource output > ---------------------------------------------------------------------------------- > > Key: WFCORE-4041 > URL: https://issues.redhat.com/browse/WFCORE-4041 > Project: WildFly Core > Issue Type: Bug > Components: Management > Reporter: Justin Cook > Assignee: Michal Petrov > Priority: Major > > Currently running /subsystem=elytron/properties-realm=ManagementRealm:read-resource() results in the output: > {code} > { > "outcome" => "success", > "result" => { > "groups-attribute" => "groups", > "groups-properties" => { > "path" => "mgmt-groups.properties", > "relative-to" => "jboss.server.config.dir" > }, > "users-properties" => { > "path" => "mgmt-users.properties", > "relative-to" => "jboss.server.config.dir", > "digest-realm-name" => "ManagementRealm" > } > } > } > {code} > which is missing the plain-text attribute -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5216) Rule compilation error when binding fields indexed with square brackets

by Mario Fusco (Jira)

[ https://issues.redhat.com/browse/DROOLS-5216?page=com.atlassian.jira.plug... ] Mario Fusco resolved DROOLS-5216. --------------------------------- Resolution: Done Fixed by https://github.com/kiegroup/drools/commit/719803b00d91c962a5aa0383c4db3a6... > Rule compilation error when binding fields indexed with square brackets > ----------------------------------------------------------------------- > > Key: DROOLS-5216 > URL: https://issues.redhat.com/browse/DROOLS-5216 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 7.35.0.Final > Reporter: Matteo Casalino > Assignee: Mario Fusco > Priority: Major > Attachments: binding-field-indexed-with-square-brackets.zip > > > Executable model rule compilation fails on patters that bind a collection field indexed with square brackets > Example of DRL that fails to compile: > {noformat} > rule "binding field indexed with square brackets" > when Pojo($firstItem : integerList[0]) > Pojo(integerList[this.integerList.size()-1] == $firstItem) > then > end > {noformat} > Error: > {noformat} > Message [id=1, level=ERROR, path=src/main/java/org/drools/reproducer/RulesE96881902F91EBF30C7D6404720A1A94RuleMethods0.java, line=29, column=138 > text=no suitable method found for bind(org.drools.model.Variable<java.util.Map>,(org.drool[...]et(0)) > method org.drools.model.PatternDSL.PatternDef.<A>bind(org.drools.model.Variable<A>,org.drools.model.functions.Function1<org.drools.reproducer.Pojo,A>) is not applicable > (inference variable A has incompatible bounds > equality constraints: java.util.Map > lower bounds: java.lang.Integer) > method org.drools.model.PatternDSL.PatternDef.<A>bind(org.drools.model.Variable<A>,org.drools.model.functions.Function1<org.drools.reproducer.Pojo,A>,org.drools.model.PatternDSL.ReactOn) is not applicable > (cannot infer type-variable(s) A > (actual and formal argument lists differ in length)) > method org.drools.model.PatternDSL.PatternDef.<A,U>bind(org.drools.model.Variable<A>,org.drools.model.Variable<U>,org.drools.model.functions.Function1<U,A>) is not applicable > (cannot infer type-variable(s) A,U > (actual and formal argument lists differ in length)) > {noformat} > The example works fine when compiling without executable model. > Furthermore, the same example expressed with OOPath fails to compile *both with and without executable model*: > {noformat} > rule "binding field indexed with square brackets in OOPath" > when Pojo($firstItem : /integerList[0]) > Pojo(/integerList[this.integerList.size()-1] == $firstItem) > then > end > {noformat} > Error without executable model: > {noformat} > Message [id=1, kieBase=binding-field-indexed-with-square-brackets, level=ERROR, path=org/drools/reproducer/rules.drl, line=4, column=0 > text=Unable to Analyse Expression /integerList[this.integerList.size()-1] == $firstItem: > [Error: Missing left node] > [Near : {... /integerList[this.integerList.size()-1] == $firstItem ....}] > {noformat} > Error with executable model: > {noformat} > Message [id=1, kieBase=binding-field-indexed-with-square-brackets, level=ERROR, path=org/drools/reproducer/rules.drl, line=-1, column=0 > text=Unknown field integerList on class java.lang.Integer] > {noformat} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5217) Executable model compilation fails when binding a list from double square bracket

by Mario Fusco (Jira)

[ https://issues.redhat.com/browse/DROOLS-5217?page=com.atlassian.jira.plug... ] Mario Fusco updated DROOLS-5217: -------------------------------- Sprint: 2020 Week 13-15 (from Mar 23) > Executable model compilation fails when binding a list from double square bracket > --------------------------------------------------------------------------------- > > Key: DROOLS-5217 > URL: https://issues.redhat.com/browse/DROOLS-5217 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 7.35.0.Final > Reporter: Matteo Casalino > Assignee: Mario Fusco > Priority: Major > Attachments: binding-list-from-double-square-bracket.zip > > > Executable model rule compilation fails when trying to bind a _List_ from a double square bracket > Example of DRL that fails to compile: > {noformat} > rule "binding field indexed with square brackets" > when $boundList: java.util.List() from [[1,2,3]] > Pojo($boundList.containsAll(integerList)) > then > end > {noformat} > Error: > {noformat} > com.github.javaparser.ParseProblemException: Encountered unexpected token: "[" "[" > at line 1, column 1. > > Was expecting one of: > > "!" > "(" > "+" > "++" > ... > {noformat} > The example works fine when compiling without executable model. > We acknowledge that there are better and more efficient ways to achieve the same result as the above example, but there are perhaps other use-cases for the double square bracket mvel expression. As it is supported in DRL, should it be supported with executable model too? -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13323) Upgrade smallrye-fault-tolerance to 4.2.0

by Radoslav Husar (Jira)

[ https://issues.redhat.com/browse/WFLY-13323?page=com.atlassian.jira.plugi... ] Radoslav Husar updated WFLY-13323: ---------------------------------- Fix Version/s: 20.0.0.Beta1 > Upgrade smallrye-fault-tolerance to 4.2.0 > ----------------------------------------- > > Key: WFLY-13323 > URL: https://issues.redhat.com/browse/WFLY-13323 > Project: WildFly > Issue Type: Component Upgrade > Components: MP Fault Tolerance > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Major > Fix For: 20.0.0.Beta1 > > > Changes: > https://github.com/smallrye/smallrye-fault-tolerance/compare/4.1.1...4.2.0 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 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 April 2020