April 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (SWSQE-1108) Update job parameters descriptions

by Filip Brychta (Jira)

Filip Brychta created SWSQE-1108: ------------------------------------ Summary: Update job parameters descriptions Key: SWSQE-1108 URL: https://issues.redhat.com/browse/SWSQE-1108 Project: Kiali QE Issue Type: QE Task Reporter: Filip Brychta Assignee: Filip Brychta Currently a user without any knowledge can't run jenkins pipelines. We need to update description of job parameters so it's clear even for user without knowledge about operator sources etc. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 3 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-1106) Update install istio to checkout deploy-kiali-operator.sh from given branch instead of using OPERATOR_VERSION_LABEL

by Filip Brychta (Jira)

[ https://issues.redhat.com/browse/SWSQE-1106?page=com.atlassian.jira.plugi... ] Filip Brychta resolved SWSQE-1106. ---------------------------------- Resolution: Done > Update install istio to checkout deploy-kiali-operator.sh from given branch instead of using OPERATOR_VERSION_LABEL > ------------------------------------------------------------------------------------------------------------------- > > Key: SWSQE-1106 > URL: https://issues.redhat.com/browse/SWSQE-1106 > Project: Kiali QE > Issue Type: QE Task > Reporter: Filip Brychta > Assignee: Filip Brychta > Priority: Major > Labels: infrastructure > > Current solution is not testing changes in yamls in given PR -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 3 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-1105) install maistra job fails for 1.12.6 operator version

by Filip Brychta (Jira)

[ https://issues.redhat.com/browse/SWSQE-1105?page=com.atlassian.jira.plugi... ] Filip Brychta resolved SWSQE-1105. ---------------------------------- Resolution: Done > install maistra job fails for 1.12.6 operator version > ----------------------------------------------------- > > Key: SWSQE-1105 > URL: https://issues.redhat.com/browse/SWSQE-1105 > Project: Kiali QE > Issue Type: Bug > Reporter: Filip Brychta > Assignee: Filip Brychta > Priority: Major > Labels: infrastructure > > KIALI_OPERATOR_TAG 1.12.6 is passed directly to OPERATOR_VERSION_LABEL which is looking for 1.12.6 branch which does not exists. It must be v1.12 branch. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13333) Openapi endpoint returns empty file if schema definition contains non ASCII character

by Paul Ferraro (Jira)

[ https://issues.redhat.com/browse/WFLY-13333?page=com.atlassian.jira.plugi... ] Paul Ferraro updated WFLY-13333: -------------------------------- Git Pull Request: https://github.com/wildfly/wildfly/pull/13171, https://github.com/wildfly/wildfly/pull/13172 (was: https://github.com/wildfly/wildfly/pull/13171) > Openapi endpoint returns empty file if schema definition contains non ASCII character > ------------------------------------------------------------------------------------- > > Key: WFLY-13333 > URL: https://issues.redhat.com/browse/WFLY-13333 > Project: WildFly > Issue Type: Bug > Components: MP OpenAPI > Affects Versions: 19.0.0.Final > Reporter: Márk Petrényi > Assignee: Paul Ferraro > Priority: Major > > Currently the {{/openapi}} endpoint returns empty file if the OpenAPI schema definition contains non ASCII characters (ie. accented letters like á,í...). > I extended the openapi quickstart for demonstration: https://github.com/petrenyi-mark/quickstart/commit/44096980ff36ff2655859f... > It seems like it is related to the content-length, since in {{OpenAPIHttpHandler}} the content-length header is set by {{String.length()}} (line 125). However before the response is actually returned, undertow validates that the actual content-length based on ByteBuffer size is not greater then the one declared in the response header. Since non ASCII characters are usually represented by 2 bytes undertow will fail, thus no content will be returned. > In {{OpenAPIHttpHandler}} setting {{string.getBytes(charset).length}} as Conetnt-Length instead of {{String.length()}} would likely resolve this issue. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13333) Openapi endpoint returns empty file if schema definition contains non ASCII character

by Paul Ferraro (Jira)

[ https://issues.redhat.com/browse/WFLY-13333?page=com.atlassian.jira.plugi... ] Paul Ferraro updated WFLY-13333: -------------------------------- Priority: Blocker (was: Major) > Openapi endpoint returns empty file if schema definition contains non ASCII character > ------------------------------------------------------------------------------------- > > Key: WFLY-13333 > URL: https://issues.redhat.com/browse/WFLY-13333 > Project: WildFly > Issue Type: Bug > Components: MP OpenAPI > Affects Versions: 19.0.0.Final > Reporter: Márk Petrényi > Assignee: Paul Ferraro > Priority: Blocker > > Currently the {{/openapi}} endpoint returns empty file if the OpenAPI schema definition contains non ASCII characters (ie. accented letters like á,í...). > I extended the openapi quickstart for demonstration: https://github.com/petrenyi-mark/quickstart/commit/44096980ff36ff2655859f... > It seems like it is related to the content-length, since in {{OpenAPIHttpHandler}} the content-length header is set by {{String.length()}} (line 125). However before the response is actually returned, undertow validates that the actual content-length based on ByteBuffer size is not greater then the one declared in the response header. Since non ASCII characters are usually represented by 2 bytes undertow will fail, thus no content will be returned. > In {{OpenAPIHttpHandler}} setting {{string.getBytes(charset).length}} as Conetnt-Length instead of {{String.length()}} would likely resolve this issue. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13334) MP Opentracing tests are not passing with a Security Manager

by Emmanuel Hugonnet (Jira)

Emmanuel Hugonnet created WFLY-13334: ---------------------------------------- Summary: MP Opentracing tests are not passing with a Security Manager Key: WFLY-13334 URL: https://issues.redhat.com/browse/WFLY-13334 Project: WildFly Issue Type: Bug Components: MP OpenTracing, Security Manager, Test Suite Affects Versions: 19.0.1.Final Reporter: Emmanuel Hugonnet Assignee: Emmanuel Hugonnet Failing tests : EarOpenTracingTestCase.testEarServicesUseDifferentTracersAfterReloadorg.wildfly.test.integration.microprofile.opentracing EarOpenTracingTestCase.testEarServicesUseDifferentTracersorg.wildfly.test.integration.microprofile.opentracing EarOpenTracingWithWeldProbeTestCase.testEarServicesUseDifferentTracersAfterReloadorg.wildfly.test.integration.microprofile.opentracing EarOpenTracingWithWeldProbeTestCase.testEarServicesUseDifferentTracersorg.wildfly.test.integration.microprofile.opentracing MultiTracerTestCase.testMultipleWarServicesUseDifferentTracersorg.wildfly.test.integration.microprofile.opentracing MultiTracerTestCase.testMultipleWarServicesUseDifferentTracersAfterReloadorg.wildfly.test.integration.microprofile.opentracing MultiWarOpenTracingTestCase.testMultipleWarServicesUseDifferentTracersorg.wildfly.test.integration.microprofile.opentracing MultiWarOpenTracingTestCase.testMultipleWarServicesUseDifferentTracersAfterReloadorg.wildfly.test.integration.microprofile.opentracing OnOffOpenTracingTestCase.testOpenTracingMultinodeServerorg.wildfly.test.integration.microprofile.opentracing ResourceWithCDITestCase.tracedEndpointYieldsSpanorg.wildfly.test.integration.microprofile.opentracing ResourceWithCustomOperationNameBeanTestCase.customOperationNameorg.wildfly.test.integration.microprofile.opentracing SimpleRestClientTestCase.clientRequestSpanJoinsServerorg.wildfly.test.integration.microprofile.opentracing SubsystemConfigurationTestCase.checkJaegerTracerAttributesorg.wildfly.test.integration.microprofile.opentracing SubsystemConfigurationTestCase.checkNoopTracerConfigurationorg.wildfly.test.integration.microprofile.opentracing 30ms 14 Failed WildCardTestCase.wildCardPathorg.wildfly.test.integration.microprofile.opentracing -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12810) Documentation for Using regex for role in Elytron

by Diana Vilkolakova (Jira)

[ https://issues.redhat.com/browse/WFLY-12810?page=com.atlassian.jira.plugi... ] Diana Vilkolakova updated WFLY-12810: ------------------------------------- Description: Add a note to community documentation about new regex role mapper that can be used in Elytron subsystem. > Documentation for Using regex for role in Elytron > ------------------------------------------------- > > Key: WFLY-12810 > URL: https://issues.redhat.com/browse/WFLY-12810 > Project: WildFly > Issue Type: Feature Request > Reporter: Diana Vilkolakova > Assignee: Diana Vilkolakova > Priority: Major > > Add a note to community documentation about new regex role mapper that can be used in Elytron subsystem. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13322) Ability to configure JSF Implementation that uses the jsf-injection module instead of copying jars

by Brad Maxwell (Jira)

[ https://issues.redhat.com/browse/WFLY-13322?page=com.atlassian.jira.plugi... ] Brad Maxwell updated WFLY-13322: -------------------------------- Description: Currently to configure a different JSF Implementation in a module, these steps below are followed: 1. $ mkdir -p modules/com/sun/jsf-impl/JSF_IMPL_NAME-JSF_VERSION 2. Copy the wildfly-jsf-injection and weld-core-jsf JAR files from EAP_HOME/modules/system/layers/base/org/jboss/as/jsf-injection/main/ to the modules/com/sun/jsf-impl/JSF_IMPL_NAME-JSF_VERSION/ subdirectory. For initial setup, the jars that need to be copied may be from modules/system/layers/base/org/jboss/as/jsf-injection/main or if an Update is applied, then it should be from the latest dir of the form system/layers/base/.overlays/layer-base-jboss-eap-7.2.z.CP/org/jboss/as/jsf-injection/main After a new Update, if a bug gets fixed in the jars, then the user needs to copy the updated jars into their custom module. It would be better if the user can just create a module with their jars and depend on the org/jboss/as/jsf-injection module and then the JSF subsystem make it work. was: Modifying modules under modules/system/ should not be required as this breaks patching and requires users to keep re applying the configuration or copying jars around when a patch is applied. The user should be able to create a module with a different JSF implementation and depend on org.jboss.as.jsf-injection or such and it work without having to modify the org.jboss.as.jsf-injection module. > Ability to configure JSF Implementation that uses the jsf-injection module instead of copying jars > -------------------------------------------------------------------------------------------------- > > Key: WFLY-13322 > URL: https://issues.redhat.com/browse/WFLY-13322 > Project: WildFly > Issue Type: Enhancement > Components: JSF > Reporter: Brad Maxwell > Assignee: Farah Juma > Priority: Major > > Currently to configure a different JSF Implementation in a module, these steps below are followed: > 1. $ mkdir -p modules/com/sun/jsf-impl/JSF_IMPL_NAME-JSF_VERSION > 2. Copy the wildfly-jsf-injection and weld-core-jsf JAR files from EAP_HOME/modules/system/layers/base/org/jboss/as/jsf-injection/main/ to the modules/com/sun/jsf-impl/JSF_IMPL_NAME-JSF_VERSION/ subdirectory. > For initial setup, the jars that need to be copied may be from modules/system/layers/base/org/jboss/as/jsf-injection/main or if an Update is applied, then it should be from the latest dir of the form system/layers/base/.overlays/layer-base-jboss-eap-7.2.z.CP/org/jboss/as/jsf-injection/main > After a new Update, if a bug gets fixed in the jars, then the user needs to copy the updated jars into their custom module. > It would be better if the user can just create a module with their jars and depend on the org/jboss/as/jsf-injection module and then the JSF subsystem make it work. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ELY-1909) Using regex for role in Elytron

by Diana Vilkolakova (Jira)

[ https://issues.redhat.com/browse/ELY-1909?page=com.atlassian.jira.plugin.... ] Diana Vilkolakova updated ELY-1909: ----------------------------------- Description: This issue is about introducing regex mapper for security roles in Elytron. > Using regex for role in Elytron > ------------------------------- > > Key: ELY-1909 > URL: https://issues.redhat.com/browse/ELY-1909 > Project: WildFly Elytron > Issue Type: Feature Request > Reporter: Diana Vilkolakova > Assignee: Diana Vilkolakova > Priority: Major > > This issue is about introducing regex mapper for security roles in Elytron. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13322) Ability to configure JSF Implementation that uses the jsf-injection module instead of copying jars

by Brad Maxwell (Jira)

[ https://issues.redhat.com/browse/WFLY-13322?page=com.atlassian.jira.plugi... ] Brad Maxwell updated WFLY-13322: -------------------------------- Summary: Ability to configure JSF Implementation that uses the jsf-injection module instead of copying jars (was: Ability to configure JSF Implementation instead of modifying the system module) > Ability to configure JSF Implementation that uses the jsf-injection module instead of copying jars > -------------------------------------------------------------------------------------------------- > > Key: WFLY-13322 > URL: https://issues.redhat.com/browse/WFLY-13322 > Project: WildFly > Issue Type: Enhancement > Components: JSF > Reporter: Brad Maxwell > Assignee: Farah Juma > Priority: Major > > Modifying modules under modules/system/ should not be required as this breaks patching and requires users to keep re applying the configuration or copying jars around when a patch is applied. > The user should be able to create a module with a different JSF implementation and depend on org.jboss.as.jsf-injection or such and it work without having to modify the org.jboss.as.jsf-injection module. -- This message was sent by Atlassian Jira (v7.13.8#713008)

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