June 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-2637) Pattern type of accumulated result is mistakenly overwritten by accumulate function type in executable model generation

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2637?page=com.atlassian.jira.plugi... ] Mario Fusco resolved DROOLS-2637. --------------------------------- Resolution: Done Fixed by https://github.com/kiegroup/drools/commit/025e5546a19966f7491acd0403b6725... > Pattern type of accumulated result is mistakenly overwritten by accumulate function type in executable model generation > ----------------------------------------------------------------------------------------------------------------------- > > Key: DROOLS-2637 > URL: https://issues.jboss.org/browse/DROOLS-2637 > Project: Drools > Issue Type: Bug > Components: core engine > Reporter: Mario Fusco > Assignee: Mario Fusco > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-2639) Pattern type of accumulated result is mistakenly overwritten by accumulate function type in executable model generation

by Mario Fusco (JIRA)

Mario Fusco created DROOLS-2639: ----------------------------------- Summary: Pattern type of accumulated result is mistakenly overwritten by accumulate function type in executable model generation Key: DROOLS-2639 URL: https://issues.jboss.org/browse/DROOLS-2639 Project: Drools Issue Type: Bug Components: core engine Reporter: Mario Fusco Assignee: Mario Fusco -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-3930) Possible file permission issues in .properties files

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3930?page=com.atlassian.jira.plugi... ] Brian Stansberry reassigned WFCORE-3930: ---------------------------------------- Assignee: Alexey Loubyansky > Possible file permission issues in .properties files > ---------------------------------------------------- > > Key: WFCORE-3930 > URL: https://issues.jboss.org/browse/WFCORE-3930 > Project: WildFly Core > Issue Type: Bug > Components: Build System > Reporter: Martin Švehla > Assignee: Alexey Loubyansky > > With new galleon build system we discovered differences in .properties files permissions. There's probably not one "true" setting, but the permissions should be reviewed to be consistent across versions (that's why I'm setting priority major, unless we decide it's problem for users). > Possible issue here is mgmt-groups.properties and application-roles.properties being readable by world. > Here are the differences between the last couple of major builds. Most important differences (imho) are: > * *.properties under /bin used to be 664, now they are 644 > * /appclient/configuration/logging.properties and /domain/configuration/logging.properties used to be 664, now they're 600 in legacy build, 644 in galleon build > * mgmt-groups.properties and application-roles.properties are 644 in galleon build (i.e. readble by world) > {code} > $ find . -type f -name '*.properties' -exec stat --format '%A %a %n' {} \; > -rw-rw-r-- 664 ./jboss-eap-6.4.20/bin/add-user.properties > -rw-rw-r-- 664 ./jboss-eap-6.4.20/bin/jboss-cli-logging.properties > -rw-rw-r-- 664 ./jboss-eap-6.4.20/appclient/configuration/logging.properties > -rw------- 600 ./jboss-eap-6.4.20/standalone/configuration/mgmt-users.properties > -rw------- 600 ./jboss-eap-6.4.20/standalone/configuration/mgmt-groups.properties > -rw------- 600 ./jboss-eap-6.4.20/standalone/configuration/application-roles.properties > -rw-rw-r-- 664 ./jboss-eap-6.4.20/standalone/configuration/logging.properties > -rw------- 600 ./jboss-eap-6.4.20/standalone/configuration/application-users.properties > -rw------- 600 ./jboss-eap-6.4.20/domain/configuration/mgmt-users.properties > -rw------- 600 ./jboss-eap-6.4.20/domain/configuration/mgmt-groups.properties > -rw------- 600 ./jboss-eap-6.4.20/domain/configuration/application-roles.properties > -rw-rw-r-- 664 ./jboss-eap-6.4.20/domain/configuration/logging.properties > -rw------- 600 ./jboss-eap-6.4.20/domain/configuration/application-users.properties > -rw-rw-r-- 664 ./jboss-eap-7.1.2/bin/add-user.properties > -rw-rw-r-- 664 ./jboss-eap-7.1.2/bin/jboss-cli-logging.properties > -rw-rw-r-- 664 ./jboss-eap-7.1.2/migration/configuration/environment.properties > -rw-rw-r-- 664 ./jboss-eap-7.1.2/migration/configuration/logging.properties > -rw-rw-r-- 664 ./jboss-eap-7.1.2/appclient/configuration/logging.properties > -rw------- 600 ./jboss-eap-7.1.2/standalone/configuration/mgmt-users.properties > -rw------- 600 ./jboss-eap-7.1.2/standalone/configuration/mgmt-groups.properties > -rw------- 600 ./jboss-eap-7.1.2/standalone/configuration/application-roles.properties > -rw-rw-r-- 664 ./jboss-eap-7.1.2/standalone/configuration/logging.properties > -rw------- 600 ./jboss-eap-7.1.2/standalone/configuration/application-users.properties > -rw-rw-r-- 664 ./jboss-eap-7.1.2/domain/configuration/default-server-logging.properties > -rw------- 600 ./jboss-eap-7.1.2/domain/configuration/mgmt-users.properties > -rw------- 600 ./jboss-eap-7.1.2/domain/configuration/mgmt-groups.properties > -rw------- 600 ./jboss-eap-7.1.2/domain/configuration/application-roles.properties > -rw-rw-r-- 664 ./jboss-eap-7.1.2/domain/configuration/logging.properties > -rw------- 600 ./jboss-eap-7.1.2/domain/configuration/application-users.properties > -rw-rw-r-- 664 ./jboss-eap-7.2.0.CD12/bin/add-user.properties > -rw-rw-r-- 664 ./jboss-eap-7.2.0.CD12/bin/jboss-cli-logging.properties > -rw-rw-r-- 664 ./jboss-eap-7.2.0.CD12/appclient/configuration/logging.properties > -rw------- 600 ./jboss-eap-7.2.0.CD12/standalone/configuration/mgmt-users.properties > -rw------- 600 ./jboss-eap-7.2.0.CD12/standalone/configuration/mgmt-groups.properties > -rw------- 600 ./jboss-eap-7.2.0.CD12/standalone/configuration/application-roles.properties > -rw-rw-r-- 664 ./jboss-eap-7.2.0.CD12/standalone/configuration/logging.properties > -rw------- 600 ./jboss-eap-7.2.0.CD12/standalone/configuration/application-users.properties > -rw------- 600 ./jboss-eap-7.2.0.CD12/domain/configuration/mgmt-users.properties > -rw------- 600 ./jboss-eap-7.2.0.CD12/domain/configuration/mgmt-groups.properties > -rw------- 600 ./jboss-eap-7.2.0.CD12/domain/configuration/application-roles.properties > -rw-rw-r-- 664 ./jboss-eap-7.2.0.CD12/domain/configuration/logging.properties > -rw------- 600 ./jboss-eap-7.2.0.CD12/domain/configuration/application-users.properties > -rw-r--r-- 644 ./wildfly-legacy-build-14.0.0.Beta1-SNAPSHOT/bin/add-user.properties > -rw-r--r-- 644 ./wildfly-legacy-build-14.0.0.Beta1-SNAPSHOT/bin/jboss-cli-logging.properties > -rw------- 600 ./wildfly-legacy-build-14.0.0.Beta1-SNAPSHOT/appclient/configuration/logging.properties > -rw------- 600 ./wildfly-legacy-build-14.0.0.Beta1-SNAPSHOT/standalone/configuration/mgmt-users.properties > -rw------- 600 ./wildfly-legacy-build-14.0.0.Beta1-SNAPSHOT/standalone/configuration/mgmt-groups.properties > -rw------- 600 ./wildfly-legacy-build-14.0.0.Beta1-SNAPSHOT/standalone/configuration/application-roles.properties > -rw------- 600 ./wildfly-legacy-build-14.0.0.Beta1-SNAPSHOT/standalone/configuration/logging.properties > -rw------- 600 ./wildfly-legacy-build-14.0.0.Beta1-SNAPSHOT/standalone/configuration/application-users.properties > -rw------- 600 ./wildfly-legacy-build-14.0.0.Beta1-SNAPSHOT/domain/configuration/default-server-logging.properties > -rw------- 600 ./wildfly-legacy-build-14.0.0.Beta1-SNAPSHOT/domain/configuration/mgmt-users.properties > -rw------- 600 ./wildfly-legacy-build-14.0.0.Beta1-SNAPSHOT/domain/configuration/mgmt-groups.properties > -rw------- 600 ./wildfly-legacy-build-14.0.0.Beta1-SNAPSHOT/domain/configuration/application-roles.properties > -rw------- 600 ./wildfly-legacy-build-14.0.0.Beta1-SNAPSHOT/domain/configuration/logging.properties > -rw------- 600 ./wildfly-legacy-build-14.0.0.Beta1-SNAPSHOT/domain/configuration/application-users.properties > -rw-r--r-- 644 ./wildfly-14.0.0.Beta1-SNAPSHOT/bin/add-user.properties > -rw-r--r-- 644 ./wildfly-14.0.0.Beta1-SNAPSHOT/bin/jboss-cli-logging.properties > -rw-r--r-- 644 ./wildfly-14.0.0.Beta1-SNAPSHOT/appclient/configuration/logging.properties > -rw------- 600 ./wildfly-14.0.0.Beta1-SNAPSHOT/standalone/configuration/mgmt-users.properties > -rw-r--r-- 644 ./wildfly-14.0.0.Beta1-SNAPSHOT/standalone/configuration/mgmt-groups.properties > -rw-r--r-- 644 ./wildfly-14.0.0.Beta1-SNAPSHOT/standalone/configuration/application-roles.properties > -rw-r--r-- 644 ./wildfly-14.0.0.Beta1-SNAPSHOT/standalone/configuration/logging.properties > -rw------- 600 ./wildfly-14.0.0.Beta1-SNAPSHOT/standalone/configuration/application-users.properties > -rw-r--r-- 644 ./wildfly-14.0.0.Beta1-SNAPSHOT/domain/configuration/default-server-logging.properties > -rw------- 600 ./wildfly-14.0.0.Beta1-SNAPSHOT/domain/configuration/mgmt-users.properties > -rw-r--r-- 644 ./wildfly-14.0.0.Beta1-SNAPSHOT/domain/configuration/mgmt-groups.properties > -rw-r--r-- 644 ./wildfly-14.0.0.Beta1-SNAPSHOT/domain/configuration/application-roles.properties > -rw-r--r-- 644 ./wildfly-14.0.0.Beta1-SNAPSHOT/domain/configuration/logging.properties > -rw------- 600 ./wildfly-14.0.0.Beta1-SNAPSHOT/domain/configuration/application-users.propertie > {code} > Note: WF build is current master (commit 7027657) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SWSQE-297) Istio 0.7.1 Deploy Error

by Guilherme Baufaker Rêgo (JIRA)

[ https://issues.jboss.org/browse/SWSQE-297?page=com.atlassian.jira.plugin.... ] Guilherme Baufaker Rêgo resolved SWSQE-297. ------------------------------------------- Resolution: Done > Istio 0.7.1 Deploy Error > ------------------------ > > Key: SWSQE-297 > URL: https://issues.jboss.org/browse/SWSQE-297 > Project: Kiali QE > Issue Type: Bug > Reporter: Matt Mahoney > Assignee: Guilherme Baufaker Rêgo > > istio-demo.yaml': No such file or directory > When I ran the playbook localhost, .~/istio/istio-0.7.1/install/kubernetes/istio-demo.yaml does not exist. Note, there is an istio-0.8.0/istio-demo.yaml > Ex: [http://jenkins2.bc.jonqe.lab.eng.bos.redhat.com:8080/job/install-istio/12...] -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-10520) Add Hibernate ORM 5.3 compatibility transformer

by Scott Marlow (JIRA)

[ https://issues.jboss.org/browse/WFLY-10520?page=com.atlassian.jira.plugin... ] Scott Marlow commented on WFLY-10520: ------------------------------------- Transformer is working at all for wildfly/testsuite/compat testing, you need to start WildFly in EE 8 mode and then just do "mvn clean install" to run tests. The server.log is mostly here (zero NoSuchMethodError errors) [https://paste.fedoraproject.org/paste/Vf~eqQXDLCt8Q76JFbfwYA] and test output is here [https://paste.fedoraproject.org/paste/vcDeCUtfsrgpcBoCt904lA]. Good progress, thanks for the tests Gail and thanks for the transformer help David! > Add Hibernate ORM 5.3 compatibility transformer > ----------------------------------------------- > > Key: WFLY-10520 > URL: https://issues.jboss.org/browse/WFLY-10520 > Project: WildFly > Issue Type: Task > Components: JPA / Hibernate > Reporter: Gail Badner > Assignee: Scott Marlow > Fix For: 14.0.0.CR1 > > > A compatibility transformer needs to be added to address Hibernate ORM 5.3 API methods that are no longer compatible with 5.1. > From https://docs.google.com/document/d/1cAVBdeQXQfpTwH0f_GKSahh_gRd7bKI6kII-w... > # Change call to org.hibernate.BasicQueryContract.getFlushMode() to instead call BasicQueryContract.getHibernateFlushMode(). > # Change call to org.hibernate.Session.getFlushMode, to instead call Session.getHibernateFlushMode() > # Modify calls to org.hibernate.Query.getFirstResult() to convert returned int, to Integer result. > # Modify calls to org.hibernate.Query.getMaxResults() to convert returned int, to Integer result, if returned int value is <= 0, null should be used, if Integer.MAX_VALUE is, the transformer should replace with null reference. > # App References to Enum org.hibernate.FlushMode.NEVER (0) should be transformed to reference FlushMode.MANUAL (0) instead. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-2638) Enumerations drop quotes when double quotes are used

by Toni Rikkola (JIRA)

Toni Rikkola created DROOLS-2638: ------------------------------------ Summary: Enumerations drop quotes when double quotes are used Key: DROOLS-2638 URL: https://issues.jboss.org/browse/DROOLS-2638 Project: Drools Issue Type: Bug Components: Enumerations Editor Reporter: Toni Rikkola Assignee: Michael Anstis https://github.com/kiegroup/kie-wb-common/pull/1890 @Rikkola The issue reported in the JIRA seem to be resolved; however I noticed (given an enumeration defined as Person.name: ['a', '"b, c"', 'd']) that the generated DRL is Person( name == "b, c" ) whereas should it be Person( name == "\"b, c\"" )? Closing and re-opening the decision table keeps the correct values selected in the table. I also tried defining the BRL fragment to use a literal value for the enumeration and this gave the same results (DRL possibly incorrect, but re-opening and editing the column was OK). I also checked Guided Rules and the DRL is equally wrong however re-opening the rule also led to the wrong enumeration value being selected in the editor (it selected the first option by default) and the DRL showing the same (i.e. I set it to "b, c" and re-opening the file selected a). -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SWSQE-302) Create base image for jenkins slaves and refactor others to use it

by Filip Brychta (JIRA)

Filip Brychta created SWSQE-302: ----------------------------------- Summary: Create base image for jenkins slaves and refactor others to use it Key: SWSQE-302 URL: https://issues.jboss.org/browse/SWSQE-302 Project: Kiali QE Issue Type: Task Reporter: Filip Brychta Assignee: Filip Brychta Currently we are using jenkins-slaves/jenkins-slave-centos-base as base image. We need our own base image with configured sudo and ssh keys. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SWSQE-301) Research Differences bewteen Istio 0.8.0 and Istio 0.7.1 to create Smoke Test

by viet nguyen (JIRA)

[ https://issues.jboss.org/browse/SWSQE-301?page=com.atlassian.jira.plugin.... ] viet nguyen commented on SWSQE-301: ----------------------------------- >From what I know *auto-sidecar injection* is one of the latest and greatest additions in Istio 0.8. It makes Istio much much friendlier to use. You still need to manually fix the deployment template. See this blog [post|https://developers.redhat.com/blog/2018/04/05/coolstore-microservice... ] about patching deployment config `oc patch`. > Research Differences bewteen Istio 0.8.0 and Istio 0.7.1 to create Smoke Test > ----------------------------------------------------------------------------- > > Key: SWSQE-301 > URL: https://issues.jboss.org/browse/SWSQE-301 > Project: Kiali QE > Issue Type: QE Task > Reporter: Guilherme Baufaker Rêgo > Assignee: Guilherme Baufaker Rêgo > > From Hayk Email > Guilherme, could you please document the major differences between Istio > 0.8.0 and 0.7.1 in a scope of having influence on Kiali, like creation > of Route Rules, other Istio objects, etc.., and write down these areas -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SWSQE-301) Research Differences bewteen Istio 0.8.0 and Istio 0.7.1 to create Smoke Test

by viet nguyen (JIRA)

[ https://issues.jboss.org/browse/SWSQE-301?page=com.atlassian.jira.plugin.... ] viet nguyen edited comment on SWSQE-301 at 6/15/18 1:36 PM: ------------------------------------------------------------ >From what I know *auto-sidecar injection* is one of the latest and greatest additions in Istio 0.8. It makes Istio much much friendlier to use. You still need to manually fix the deployment template. See this blog [post|https://developers.redhat.com/blog/2018/04/05/coolstore-microservice...] about patching deployment config `oc patch`. was (Author: vietn): >From what I know *auto-sidecar injection* is one of the latest and greatest additions in Istio 0.8. It makes Istio much much friendlier to use. You still need to manually fix the deployment template. See this blog [post|https://developers.redhat.com/blog/2018/04/05/coolstore-microservice... ] about patching deployment config `oc patch`. > Research Differences bewteen Istio 0.8.0 and Istio 0.7.1 to create Smoke Test > ----------------------------------------------------------------------------- > > Key: SWSQE-301 > URL: https://issues.jboss.org/browse/SWSQE-301 > Project: Kiali QE > Issue Type: QE Task > Reporter: Guilherme Baufaker Rêgo > Assignee: Guilherme Baufaker Rêgo > > From Hayk Email > Guilherme, could you please document the major differences between Istio > 0.8.0 and 0.7.1 in a scope of having influence on Kiali, like creation > of Route Rules, other Istio objects, etc.., and write down these areas -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ELY-1493) java.util.concurrent.TimeoutException on slow machines

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/ELY-1493?page=com.atlassian.jira.plugin.s... ] Jan Kalina commented on ELY-1493: --------------------------------- Second PR: prolonged timeouts yet - I have not found any locking issue which could cause longer test run :/ > java.util.concurrent.TimeoutException on slow machines > ------------------------------------------------------ > > Key: ELY-1493 > URL: https://issues.jboss.org/browse/ELY-1493 > Project: WildFly Elytron > Issue Type: Bug > Components: Testsuite > Affects Versions: 1.2.0.Beta11 > Reporter: Martin Choma > Assignee: Jan Kalina > Fix For: 1.2.0.Beta12 > > > On solaris 10 (slow machine) there occured timeout for task task2Future.get(1, TimeUnit.SECONDS) on line 492. > Prolong timeout will probably reduce occurences. > {noformat} > java.lang.RuntimeException: java.util.concurrent.ExecutionException: java.util.concurrent.TimeoutException > at org.wildfly.security.credential.store.KeystorePasswordStoreTest.testAccessFromMultipleCredentialStores(KeystorePasswordStoreTest.java:459) > at org.wildfly.security.credential.store.KeystorePasswordStoreTest.testParallelAccessToCS(KeystorePasswordStoreTest.java:439) > Caused by: java.util.concurrent.ExecutionException: java.util.concurrent.TimeoutException > at java.base/java.util.concurrent.FutureTask.report(FutureTask.java:122) > at java.base/java.util.concurrent.FutureTask.get(FutureTask.java:205) > at org.wildfly.security.credential.store.KeystorePasswordStoreTest.testAccessFromMultipleCredentialStores(KeystorePasswordStoreTest.java:457) > ... 1 more > Caused by: java.util.concurrent.TimeoutException > at java.base/java.util.concurrent.FutureTask.get(FutureTask.java:204) > at org.wildfly.security.credential.store.KeystorePasswordStoreTest$1.call(KeystorePasswordStoreTest.java:492) > at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264) > at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167) > at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641) > at java.base/java.lang.Thread.run(Thread.java:844) > {noformat} > [1] https://jenkins.hosts.mwqe.eng.bos.redhat.com/hudson/view/EAP7/view/EAP7-... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

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 June 2018