September 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-13898) Bootable JAR/Galleon - HTTP 500 is returned by some RESTEasy tests

by Fabio Burzigotti (Jira)

Fabio Burzigotti created WFLY-13898: --------------------------------------- Summary: Bootable JAR/Galleon - HTTP 500 is returned by some RESTEasy tests Key: WFLY-13898 URL: https://issues.redhat.com/browse/WFLY-13898 Project: WildFly Issue Type: Task Components: Build System Reporter: Fabio Burzigotti Assignee: Jean Francois Denise I set the component to {{Build System}} because this only happens with Bootable JAR and - as [~jdenise] noticed - it's related with Galleon. This is about some tests in the RESTEasy TS which has been adapted to execute against bootable JARs through a specific profile [1]. The tests are running successfully with WildFly 20.0.1.Final (the {{ejb}} layer needs to be removed for this experiment to be run) but fail against 21.0.0.Beta1, so it is a regression. Also, the tests are passing when the TS is executed against a distributed WildFly version, and only fail when the server is packaged via the {wildfly-jar-maven-plugin}}. There are 108 tests failing but htis JIRA focuses on those failing because of the following error: {code} RESTEASY002005: Failed executing POST /all/a/z: org.jboss.resteasy.core.NoMessageBodyWriterFoundFailure: Could not find MessageBodyWriter for response object of type: org.jboss.resteasy.test.validation.resource.ValidationFoo of media type: application/xml;charset=UTF-8 {code} hence I guess serialization issues when the request accept header is not {{application/json}}, e.g. {{org.jboss.resteasy.test.validation.ValidationTest}} *Steps to reproduce*: 1. clone https://github.com/fabiobrz/Resteasy/tree/bootable-jar-support 2. build RESTEasy: {code} $ mvn install -Dmaven.test.skip=true -Dmaven.reppo.local=/home/my-local-repo {code} 3. run the test against WF 21.0.0.Beta1: {code} mvn clean verify -am -pl integration-tests -Dmaven.reppo.local=/home/my-local-repo -Dserver.version=21.0.0.Beta1 -Dtest=org.jboss.resteasy.test.validation.ValidationTest {code} The test should pass 4. run the test against WF 21.0.0.Beta1 with bootable JAR: {code} mvn clean verify -am -pl integration-tests -Dmaven.reppo.local=/home/my-local-repo -Dserver.version=21.0.0.Beta1 -Dtest=org.jboss.resteasy.test.validation.ValidationTest -Ddisable.microprofile.tests -Dserver.home=foo -Dts.bootable {code} The test should fail 5. run the test against WF 20.0.1.Final with bootable JAR: {code} mvn clean verify -am -pl integration-tests -Dmaven.reppo.local=/home/my-local-repo -Dserver.version=20.0.0.Final -Dtest=org.jboss.resteasy.test.validation.ValidationTest -Ddisable.microprofile.tests -Dserver.home=foo -Dts.bootable {code} The test should pass [1] https://github.com/resteasy/Resteasy/pull/2526/files#diff-8c7ea03eb619e46... -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-5675) DMN Validation reporting a Gap for fully covered range constrained type

by Jan Stastny (Jira)

Jan Stastny created DROOLS-5675: ----------------------------------- Summary: DMN Validation reporting a Gap for fully covered range constrained type Key: DROOLS-5675 URL: https://issues.redhat.com/browse/DROOLS-5675 Project: Drools Issue Type: Bug Components: DMN Editor Affects Versions: 7.44.0.Final Reporter: Jan Stastny Assignee: Guilherme Gomes Attachments: gap-constraint.gif Validation is reporting Gaps in constrained data type even though the matched range equals the constrained type range. Happens for both imported and structure data types. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-4844) Alpha Network Compiler should be an option in Kie-API

by Luca Molteni (Jira)

[ https://issues.redhat.com/browse/DROOLS-4844?page=com.atlassian.jira.plug... ] Luca Molteni updated DROOLS-4844: --------------------------------- Sprint: 2020 Week 40-42 (from Sep 28) > Alpha Network Compiler should be an option in Kie-API > ----------------------------------------------------- > > Key: DROOLS-4844 > URL: https://issues.redhat.com/browse/DROOLS-4844 > Project: Drools > Issue Type: Feature Request > Reporter: Luca Molteni > Assignee: Luca Molteni > Priority: Major > Labels: good-first-issue > > In the `kie.internal` package extending `SingleValueKieBaseOption` > Currently it's a boolean in KieContainerImpl -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-2836) Support compiling of a Big Rule

by Luca Molteni (Jira)

[ https://issues.redhat.com/browse/DROOLS-2836?page=com.atlassian.jira.plug... ] Luca Molteni updated DROOLS-2836: --------------------------------- Sprint: 2020 Week 40-42 (from Sep 28) > Support compiling of a Big Rule > ------------------------------- > > Key: DROOLS-2836 > URL: https://issues.redhat.com/browse/DROOLS-2836 > Project: Drools > Issue Type: Bug > Reporter: Luca Molteni > Assignee: Luca Molteni > Priority: Major > > RemoveRuleTest.testRemoveBigRule > java.lang.RuntimeException: This is a bug. Please contact the development team: > [org/drools/core/reteoo/compiled/Compiledorg_drools_compiler_test_SimpleFactNetwork8aecdf1db7f9b4f4abcbafdd301c63d7c.java (6279:25) : package org.drools.compiler.test does not exist, org/drools/core/reteoo/compiled/Compiledorg_drools_compiler_test_SimpleFactNetwork8aecdf1db7f9b4f4abcbafdd301c63d7c.java (6279:69) : package org.drools.compiler.test does not exist, org/drools/core/reteoo/compiled/Compiledorg_drools_compiler_test_SimpleFactNetwork8aecdf1db7f9b4f4abcbafdd301c63d7c.java (7899:25) : package org.drools.compiler.test does not exist, org/drools/core/reteoo/compiled/Compiledorg_drools_compiler_test_SimpleFactNetwork8aecdf1db7f9b4f4abcbafdd301c63d7c.java (7899:69) : package org.drools.compiler.test does not exist] -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years

1
0
0 / 0

[JBoss JIRA] (SWSQE-1210) UI Automations - VS and DR Details adjustements

by Hayk Hovsepyan (Jira)

[ https://issues.redhat.com/browse/SWSQE-1210?page=com.atlassian.jira.plugi... ] Hayk Hovsepyan resolved SWSQE-1210. ----------------------------------- Resolution: Done Merged: https://github.com/Kiali-QE/kiali-qe-python/pull/327 Cherry-pick https://github.com/Kiali-QE/kiali-qe-python/pull/332 > UI Automations - VS and DR Details adjustements > ----------------------------------------------- > > Key: SWSQE-1210 > URL: https://issues.redhat.com/browse/SWSQE-1210 > Project: Kiali QE > Issue Type: QE Task > Reporter: Hayk Hovsepyan > Assignee: Hayk Hovsepyan > Priority: Major > Labels: automation > > https://github.com/kiali/kiali-ui/pull/1904 -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-5141) Upgrade JBoss Marshalling from 2.0.9.Final to 2.0.10.Final

by Ivo Studensky (Jira)

[ https://issues.redhat.com/browse/WFCORE-5141?page=com.atlassian.jira.plug... ] Ivo Studensky moved JBEAP-20252 to WFCORE-5141: ----------------------------------------------- Project: WildFly Core (was: JBoss Enterprise Application Platform) Key: WFCORE-5141 (was: JBEAP-20252) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: Build System (was: Build System) Affects Version/s: (was: 7.3.3.GA) > Upgrade JBoss Marshalling from 2.0.9.Final to 2.0.10.Final > ---------------------------------------------------------- > > Key: WFCORE-5141 > URL: https://issues.redhat.com/browse/WFCORE-5141 > Project: WildFly Core > Issue Type: Component Upgrade > Components: Build System > Reporter: Ivo Studensky > Assignee: Ivo Studensky > Priority: Major > -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-5141) Upgrade JBoss Marshalling from 2.0.9.Final to 2.0.10.Final

by Ivo Studensky (Jira)

[ https://issues.redhat.com/browse/WFCORE-5141?page=com.atlassian.jira.plug... ] Ivo Studensky updated WFCORE-5141: ---------------------------------- Labels: downstream_dependency (was: ) > Upgrade JBoss Marshalling from 2.0.9.Final to 2.0.10.Final > ---------------------------------------------------------- > > Key: WFCORE-5141 > URL: https://issues.redhat.com/browse/WFCORE-5141 > Project: WildFly Core > Issue Type: Component Upgrade > Components: Build System > Reporter: Ivo Studensky > Assignee: Ivo Studensky > Priority: Major > Labels: downstream_dependency > -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-5673) [DMN Designer] Validation fails when an included node is added on a DRD

by Guilherme Gomes (Jira)

[ https://issues.redhat.com/browse/DROOLS-5673?page=com.atlassian.jira.plug... ] Guilherme Gomes updated DROOLS-5673: ------------------------------------ Summary: [DMN Designer] Validation fails when an included node is added on a DRD (was: [DMN Designer] Validation fails when the included node is added on a DRD) > [DMN Designer] Validation fails when an included node is added on a DRD > ----------------------------------------------------------------------- > > Key: DROOLS-5673 > URL: https://issues.redhat.com/browse/DROOLS-5673 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Reporter: Guilherme Gomes > Assignee: Guilherme Gomes > Priority: Blocker > Attachments: bug.gif, model.dmn, reproducer.dmn > > > Validation is failing when users add an included node is into a DRD. > Actual: When users try to add a included node on a DRD, the "Decision Components" component shows duplicated elements, and the diagram validation fails with an infinite loading: > !bug.gif|width=600! > Expected: Users should not see duplicated elements, and the validation shouldn't fail. > To reproduce, import both models on this JIRA, and open the "reproducer.dmn" by following the steps in the GIF. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-5673) [DMN Designer] Validation fails when the included node is added on a DRD

by Guilherme Gomes (Jira)

Guilherme Gomes created DROOLS-5673: --------------------------------------- Summary: [DMN Designer] Validation fails when the included node is added on a DRD Key: DROOLS-5673 URL: https://issues.redhat.com/browse/DROOLS-5673 Project: Drools Issue Type: Bug Components: DMN Editor Reporter: Guilherme Gomes Assignee: Guilherme Gomes Attachments: bug.gif, model.dmn, reproducer.dmn Validation is failing when users add an included node is into a DRD. Actual: When users try to add a included node on a DRD, the "Decision Components" component shows duplicated elements, and the diagram validation fails with an infinite loading: !bug.gif|width=600! Expected: Users should not see duplicated elements, and the validation shouldn't fail. To reproduce, import both models on this JIRA, and open the "reproducer.dmn" by following the steps in the GIF. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years

1
0
0 / 0

[JBoss JIRA] (JBCLUSTER-316) remoteingress to patch ClusterIngress with certificate bundle

by James Harrington (Jira)

James Harrington created JBCLUSTER-316: ------------------------------------------ Summary: remoteingress to patch ClusterIngress with certificate bundle Key: JBCLUSTER-316 URL: https://issues.redhat.com/browse/JBCLUSTER-316 Project: JBoss Clustering Issue Type: Feature Request Reporter: James Harrington Assignee: Paul Ferraro Once a cluster is installed Hive should patch a cluster's ingresscontroller with the new certificate bundle from Lets Encrypt to enable the console URL to work as soon as those certificates are available. Hive's remoteingress controller [here|https://github.com/openshift/hive/blob/master/pkg/controller/remotei...] used to do exactly this by creating a new ingresscontroller object in the openshift-ingress-operator namespace but raced with the cloud-ingress-operator to manage it so it was disabled [here|https://gitlab.cee.redhat.com/service/app-interface/-/blob/master/da...]. I’m not sure if we can replace creating the entire ingresscontroller or just patch the new `.spec.defaultCertificate` to be the new certificate bundle. The piece I don’t know about is if the cluster-ingress-operator will load in the new certificates or do we have to completely replace the object? For example cloud-ingress-operator has to replace the entire ingresscontroller CR to have it change the load balancer from external to internal, I suspect the cert patch will work since the cert isn’t terminated on the ELB. The defaultCertificate ref is in the ingresscontroller spec Hive was updating it [here|https://github.com/openshift/hive/blob/master/pkg/controller/remotei...] This controller likely raced with cloud-ingress-operator because they were both watching and reconciling the same object. Maybe we could enable this controller but disable the watch when “ActiveAPIURLOverride” is set in the ClusterDeployment? Though that doesn’t feel right. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira September 2020