January 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFWIP-291) Log messages from io.smallrye.openapi don't have message ID

by Darran Lofthouse (Jira)

[ https://issues.redhat.com/browse/WFWIP-291?page=com.atlassian.jira.plugin... ] Darran Lofthouse commented on WFWIP-291: ---------------------------------------- Additionally there is also a general issue in that we can not impose our own logging formats on third party projects pulled into WildFly. If a third party project throws an Exception we can catch we may have an opportunity to catch and log with an ID or rethrow with an ID but we don't have options to intercept messages directly logged. Having said that it does seem SmallRye will be receptive to having support added to internatinalised messages with IDs but as with the comment from Paul this would not cover messages at debug or trace level. > Log messages from io.smallrye.openapi don't have message ID > ----------------------------------------------------------- > > Key: WFWIP-291 > URL: https://issues.redhat.com/browse/WFWIP-291 > Project: WildFly WIP > Issue Type: Bug > Components: MP OpenAPI > Reporter: Fabio Burzigotti > Assignee: Paul Ferraro > Priority: Major > > Messages logged by io.smallrye.openapi don't have assigned ID: > {code} > 2020-01-05 16:58:49,225 DEBUG [io.smallrye.openapi.runtime.util.SchemaFactory] (MSC service thread 1-4) Processing a single @Schema annotation. > 2020-01-05 16:58:49,225 DEBUG [io.smallrye.openapi.runtime.scanner.OpenApiAnnotationScanner] (MSC service thread 1-4) Processing a single @Response annotation. > 2020-01-05 16:58:49,225 DEBUG [io.smallrye.openapi.runtime.scanner.OpenApiAnnotationScanner] (MSC service thread 1-4) Processing jax-rs method: {0} > 2020-01-05 16:58:49,225 DEBUG [io.smallrye.openapi.runtime.scanner.OpenApiDataObjectScanner] (MSC service thread 1-4) Starting processing with root: java.lang.String > {code} > A search in SmallRye implementation seems to show that IDs are not used even when level is WARN: > {code} > $ find . -name '*.*' -type f -print0 | xargs -0 grep --color -n -e 'LOG.warn' > ./implementation/src/main/java/io/smallrye/openapi/runtime/scanner/ParameterProcessor.java:551: LOG.warnf("Matrix parameter references missing path segment: %s", segmentName); > ./implementation/src/main/java/io/smallrye/openapi/runtime/scanner/ParameterProcessor.java:1147: LOG.warnf("Value '%s' is not a valid %s default", stringValue, primitive.name().toLowerCase()); > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 5 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-1048) Testcases - Kiali Validations sync-up

by Hayk Hovsepyan (Jira)

[ https://issues.redhat.com/browse/SWSQE-1048?page=com.atlassian.jira.plugi... ] Hayk Hovsepyan edited comment on SWSQE-1048 at 1/7/20 3:24 AM: --------------------------------------------------------------- "More than one Destination Rule for the same host subset combination" error text is shows in fact: "More than one DestinationRules for the same host subset combination" was (Author: hhovsepy): "More than one Destination Rule for the same host subset combination" error text before was a different one. > Testcases - Kiali Validations sync-up > ------------------------------------- > > Key: SWSQE-1048 > URL: https://issues.redhat.com/browse/SWSQE-1048 > Project: Kiali QE > Issue Type: Sub-task > Reporter: Hayk Hovsepyan > Assignee: Sunil Kondkar > Priority: Major > > Sync up all validations from https://kiali.io/documentation/validations/ with Polarion estcases. > Make sure all validations have up-to-date testcases in Polarion. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4902) Can not use mod operators (%) in when clause.

by Mario Fusco (Jira)

[ https://issues.redhat.com/browse/DROOLS-4902?page=com.atlassian.jira.plug... ] Mario Fusco resolved DROOLS-4902. --------------------------------- Resolution: Done Fixed in mvel with https://github.com/mvel/mvel/commit/691466dd5657317a421792dfb1c366394288c1fe In the meanwhile you can workaround this issue with additional parenthesis like in: {code} Number( (this % 5) == 0 ) {code} > Can not use mod operators (%) in when clause. > --------------------------------------------- > > Key: DROOLS-4902 > URL: https://issues.redhat.com/browse/DROOLS-4902 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 7.31.0.Final > Reporter: xb l > Assignee: Mario Fusco > Priority: Major > > When I study drools , I write a rule use divide operator > {code:java} > rule "Buzz" salience 2 > when > $n: Number( this / 5 == 3 ) > then > System.out.println("Buzz"); > end > {code} > It's OK. > But: > {code:java} > rule "Buzz" salience 2 > when > $n: Number( this % 5 == 0 ) > then > System.out.println("Buzz"); > end > {code} > Report parser error: Unable to Analyse Expression this % 5 == 0: > The drools document mentioned the same example: > Person( age > 100 && ( age % 10 == 0 ) ) > % is Multiplicative operators, why parser error? -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 5 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-1048) Testcases - Kiali Validations sync-up

by Hayk Hovsepyan (Jira)

[ https://issues.redhat.com/browse/SWSQE-1048?page=com.atlassian.jira.plugi... ] Hayk Hovsepyan commented on SWSQE-1048: --------------------------------------- "mTLS settings of a non-local Destination Rule are overridden" exception, v10 in example is typo and causing other warning which confuses, should be v1. > Testcases - Kiali Validations sync-up > ------------------------------------- > > Key: SWSQE-1048 > URL: https://issues.redhat.com/browse/SWSQE-1048 > Project: Kiali QE > Issue Type: Sub-task > Reporter: Hayk Hovsepyan > Assignee: Sunil Kondkar > Priority: Major > > Sync up all validations from https://kiali.io/documentation/validations/ with Polarion estcases. > Make sure all validations have up-to-date testcases in Polarion. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4903) In constraints fail to compile if negated or inside a forall pattern

by Matteo Casalino (Jira)

[ https://issues.redhat.com/browse/DROOLS-4903?page=com.atlassian.jira.plug... ] Matteo Casalino updated DROOLS-4903: ------------------------------------ Description: It appears that the KieBuilder fails to compile the following pattern: {noformat} Pojo(!(x in (1,2,3))) {noformat} returning the following error: {noformat} Error Messages: Message [id=1, kieBase=defaultKieBase, level=ERROR, path=rules.drl, line=4, column=0 text=Unable to Analyse Expression !(x in (1,2,3)): [Error: unexpected token: ,2] [Near : {... !(x in (1,2,3)) ....}] {noformat} Furthermore, as of Drools 7.29.0.Final, the following form will also fail to compile: {noformat} forall(Pojo(y==42, x in (1,2,3))) {noformat} with the following error: {noformat} Error Messages: Message [id=1, kieBase=defaultKieBase, level=ERROR, path=rules.drl, line=4, column=0 text=Unable to Analyse Expression !(y==42) || !(x in (1,2,3)): [Error: unexpected token: ,2] [Near : {... !(y==42) || !(x in (1,2,3)) ....}] {noformat} The latter is likely a consequence of the negation introduced by [DROOLS-4632], [DROOLS-4633] was: It appears that the KieBuilder fails to compile the following pattern: {noformat} Pojo(!(x in (1,2,3))) {noformat} returning the following error: {noformat} Error Messages: Message [id=1, kieBase=defaultKieBase, level=ERROR, path=rules.drl, line=4, column=0 text=Unable to Analyse Expression !(x in (1,2,3)): [Error: unexpected token: ,2] [Near : {... !(x in (1,2,3)) ....}] {noformat} Furthermore, as of Drools 7.29.0.Final, the following form will also fail to compile: {noformat} forall(Pojo(y==42, x in (1,2,3))) {noformat} with the following error: {noformat} Error Messages: Message [id=1, kieBase=defaultKieBase, level=ERROR, path=rules.drl, line=4, column=0 text=Unable to Analyse Expression !(y==42) || !(x in (1,2,3)): [Error: unexpected token: ,2] [Near : {... !(y==42) || !(x in (1,2,3)) ....}] {noformat} The latter is likely a consequence of the negation introduced by [DROOLS-4632|https://issues.redhat.com/browse/DROOLS-4632], [DROOLS-4633][https://issues.redhat.com/browse/DROOLS-4633] > In constraints fail to compile if negated or inside a forall pattern > -------------------------------------------------------------------- > > Key: DROOLS-4903 > URL: https://issues.redhat.com/browse/DROOLS-4903 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 7.31.0.Final > Reporter: Matteo Casalino > Assignee: Mario Fusco > Priority: Major > Attachments: in-constraint-negation.tgz > > > It appears that the KieBuilder fails to compile the following pattern: > {noformat} > Pojo(!(x in (1,2,3))) > {noformat} > returning the following error: > {noformat} > Error Messages: > Message [id=1, kieBase=defaultKieBase, level=ERROR, path=rules.drl, line=4, column=0 > text=Unable to Analyse Expression !(x in (1,2,3)): > [Error: unexpected token: ,2] > [Near : {... !(x in (1,2,3)) ....}] > {noformat} > Furthermore, as of Drools 7.29.0.Final, the following form will also fail to compile: > {noformat} > forall(Pojo(y==42, x in (1,2,3))) > {noformat} > with the following error: > {noformat} > Error Messages: > Message [id=1, kieBase=defaultKieBase, level=ERROR, path=rules.drl, line=4, column=0 > text=Unable to Analyse Expression !(y==42) || !(x in (1,2,3)): > [Error: unexpected token: ,2] > [Near : {... !(y==42) || !(x in (1,2,3)) ....}] > {noformat} > The latter is likely a consequence of the negation introduced by [DROOLS-4632], [DROOLS-4633] -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4903) In constraints fail to compile if negated or inside a forall pattern

by Matteo Casalino (Jira)

[ https://issues.redhat.com/browse/DROOLS-4903?page=com.atlassian.jira.plug... ] Matteo Casalino updated DROOLS-4903: ------------------------------------ Description: It appears that the KieBuilder fails to compile the following pattern: {noformat} Pojo(!(x in (1,2,3))) {noformat} returning the following error: {noformat} Error Messages: Message [id=1, kieBase=defaultKieBase, level=ERROR, path=rules.drl, line=4, column=0 text=Unable to Analyse Expression !(x in (1,2,3)): [Error: unexpected token: ,2] [Near : {... !(x in (1,2,3)) ....}] {noformat} Furthermore, as of Drools 7.29.0.Final, the following form will also fail to compile: {noformat} forall(Pojo(y==42, x in (1,2,3))) {noformat} with the following error: {noformat} Error Messages: Message [id=1, kieBase=defaultKieBase, level=ERROR, path=rules.drl, line=4, column=0 text=Unable to Analyse Expression !(y==42) || !(x in (1,2,3)): [Error: unexpected token: ,2] [Near : {... !(y==42) || !(x in (1,2,3)) ....}] {noformat} The latter is likely a consequence of the negation introduced by [DROOLS-4632|https://issues.redhat.com/browse/DROOLS-4632], [DROOLS-4633][https://issues.redhat.com/browse/DROOLS-4633] was: It appears that the KieBuilder fails to compile the following pattern: {noformat} Pojo(!(x in (1,2,3))) {noformat} returning the following error: {noformat} Error Messages: Message [id=1, kieBase=defaultKieBase, level=ERROR, path=rules.drl, line=4, column=0 text=Unable to Analyse Expression !(x in (1,2,3)): [Error: unexpected token: ,2] [Near : {... !(x in (1,2,3)) ....}] {noformat} Furthermore, as of Drools 7.29.0.Final, the following form will also fail to compile: {noformat} forall(Pojo(y==42, x in (1,2,3))) {noformat} with the following error: {noformat} Error Messages: Message [id=1, kieBase=defaultKieBase, level=ERROR, path=rules.drl, line=4, column=0 text=Unable to Analyse Expression !(y==42) || !(x in (1,2,3)): [Error: unexpected token: ,2] [Near : {... !(y==42) || !(x in (1,2,3)) ....}] {noformat} The latter is likely a consequence of the negation introduced by [DROOLS-4632|https://issues.redhat.com/browse/DROOLS-4632] > In constraints fail to compile if negated or inside a forall pattern > -------------------------------------------------------------------- > > Key: DROOLS-4903 > URL: https://issues.redhat.com/browse/DROOLS-4903 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 7.31.0.Final > Reporter: Matteo Casalino > Assignee: Mario Fusco > Priority: Major > Attachments: in-constraint-negation.tgz > > > It appears that the KieBuilder fails to compile the following pattern: > {noformat} > Pojo(!(x in (1,2,3))) > {noformat} > returning the following error: > {noformat} > Error Messages: > Message [id=1, kieBase=defaultKieBase, level=ERROR, path=rules.drl, line=4, column=0 > text=Unable to Analyse Expression !(x in (1,2,3)): > [Error: unexpected token: ,2] > [Near : {... !(x in (1,2,3)) ....}] > {noformat} > Furthermore, as of Drools 7.29.0.Final, the following form will also fail to compile: > {noformat} > forall(Pojo(y==42, x in (1,2,3))) > {noformat} > with the following error: > {noformat} > Error Messages: > Message [id=1, kieBase=defaultKieBase, level=ERROR, path=rules.drl, line=4, column=0 > text=Unable to Analyse Expression !(y==42) || !(x in (1,2,3)): > [Error: unexpected token: ,2] > [Near : {... !(y==42) || !(x in (1,2,3)) ....}] > {noformat} > The latter is likely a consequence of the negation introduced by [DROOLS-4632|https://issues.redhat.com/browse/DROOLS-4632], [DROOLS-4633][https://issues.redhat.com/browse/DROOLS-4633] -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4903) In constraints fail to compile if negated or inside a forall pattern

by Mario Fusco (Jira)

[ https://issues.redhat.com/browse/DROOLS-4903?page=com.atlassian.jira.plug... ] Mario Fusco updated DROOLS-4903: -------------------------------- Sprint: 2020 Week 01-03 (from Dec 30) > In constraints fail to compile if negated or inside a forall pattern > -------------------------------------------------------------------- > > Key: DROOLS-4903 > URL: https://issues.redhat.com/browse/DROOLS-4903 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 7.31.0.Final > Reporter: Matteo Casalino > Assignee: Mario Fusco > Priority: Major > Attachments: in-constraint-negation.tgz > > > It appears that the KieBuilder fails to compile the following pattern: > {noformat} > Pojo(!(x in (1,2,3))) > {noformat} > returning the following error: > {noformat} > Error Messages: > Message [id=1, kieBase=defaultKieBase, level=ERROR, path=rules.drl, line=4, column=0 > text=Unable to Analyse Expression !(x in (1,2,3)): > [Error: unexpected token: ,2] > [Near : {... !(x in (1,2,3)) ....}] > {noformat} > Furthermore, as of Drools 7.29.0.Final, the following form will also fail to compile: > {noformat} > forall(Pojo(y==42, x in (1,2,3))) > {noformat} > with the following error: > {noformat} > Error Messages: > Message [id=1, kieBase=defaultKieBase, level=ERROR, path=rules.drl, line=4, column=0 > text=Unable to Analyse Expression !(y==42) || !(x in (1,2,3)): > [Error: unexpected token: ,2] > [Near : {... !(y==42) || !(x in (1,2,3)) ....}] > {noformat} > The latter is likely a consequence of the negation introduced by [DROOLS-4632|https://issues.redhat.com/browse/DROOLS-4632] -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12931) Upgrade Undertow Schema to 11.0

by Flavia Rainone (Jira)

[ https://issues.redhat.com/browse/WFLY-12931?page=com.atlassian.jira.plugi... ] Flavia Rainone updated WFLY-12931: ---------------------------------- Component/s: Web (Undertow) > Upgrade Undertow Schema to 11.0 > ------------------------------- > > Key: WFLY-12931 > URL: https://issues.redhat.com/browse/WFLY-12931 > Project: WildFly > Issue Type: Task > Components: Web (Undertow) > Reporter: Flavia Rainone > Assignee: Flavia Rainone > Priority: Major > > Upgrade the schema version to 11.0 -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12933) Add documentation on the Undertow subsystem attributes

by Flavia Rainone (Jira)

[ https://issues.redhat.com/browse/WFLY-12933?page=com.atlassian.jira.plugi... ] Flavia Rainone updated WFLY-12933: ---------------------------------- Component/s: Documentation > Add documentation on the Undertow subsystem attributes > ------------------------------------------------------ > > Key: WFLY-12933 > URL: https://issues.redhat.com/browse/WFLY-12933 > Project: WildFly > Issue Type: Task > Components: Documentation > Reporter: Flavia Rainone > Assignee: Flavia Rainone > Priority: Minor > > Currently the Admin Guide for Undertow subsystem does not have a list of the subsystem attributes. Add that to the documentation. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12932) Test UndertowService config with subsystem attributes

by Flavia Rainone (Jira)

[ https://issues.redhat.com/browse/WFLY-12932?page=com.atlassian.jira.plugi... ] Flavia Rainone updated WFLY-12932: ---------------------------------- Component/s: Web (Undertow) > Test UndertowService config with subsystem attributes > ----------------------------------------------------- > > Key: WFLY-12932 > URL: https://issues.redhat.com/browse/WFLY-12932 > Project: WildFly > Issue Type: Task > Components: Web (Undertow) > Reporter: Flavia Rainone > Assignee: Flavia Rainone > Priority: Minor > > Currently the tests dont verify if the Undertow config reflects in the correct configuration in UndertowService. Add that to the test suite. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 5 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 January 2020