August 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-4042) "filter-spec" attribute of socket-handler contains non existent "filter" alternative

by Claudio Miranda (JIRA)

[ https://issues.jboss.org/browse/WFCORE-4042?page=com.atlassian.jira.plugi... ] Claudio Miranda updated WFCORE-4042: ------------------------------------ Description: The socket-handler resource, contains an attribute "filter-spec" and the "alternatives" contains a non existent "filter" attribute {code} "filter-spec" => { "type" => STRING, "description" => "A filter expression value to define a filter. Example for a filter that does not match a pattern: not(match(\"JBAS.*\"))", "expressions-allowed" => true, "required" => false, "nillable" => true, "alternatives" => ["filter"], "min-length" => 1L, "max-length" => 2147483647L, "access-type" => "read-write", "storage" => "configuration", "restart-required" => "no-services" }, {code} I counted the following resources affected by the issue. {code} /logging-profile=*/async-handler=* /logging-profile=*/console-handler=* /logging-profile=*/custom-handler=* /logging-profile=*/file-handler=* /logging-profile=*/periodic-rotating-file-handler=* /logging-profile=*/periodic-size-rotating-file-handler=* /logging-profile=*/size-rotating-file-handler=* /logging-profile=*/socket-handler=* /logging-profile=*/root-logger=ROOT /periodic-size-rotating-file-handler=* /socket-handler=* {code} In HAL we use the metadata to validate user input and in this case, we undefine the alternative attribute the user didn't set, "filter", resulting in an error because the attribute doesn't exist. I did a workaround, but would be interesting to fix the alternatives metadata. was: The socket-handler resource, contains an attribute "filter-spec" and the "alternatives" contains a non existent "filter" attribute {code} "filter-spec" => { "type" => STRING, "description" => "A filter expression value to define a filter. Example for a filter that does not match a pattern: not(match(\"JBAS.*\"))", "expressions-allowed" => true, "required" => false, "nillable" => true, "alternatives" => ["filter"], "min-length" => 1L, "max-length" => 2147483647L, "access-type" => "read-write", "storage" => "configuration", "restart-required" => "no-services" }, {code} I counted the following resources affected by the issue. {code} /logging-profile=*/async-handler=* /logging-profile=*/console-handler=* /logging-profile=*/custom-handler=* /logging-profile=*/file-handler=* /logging-profile=*/periodic-rotating-file-handler=* /logging-profile=*/periodic-size-rotating-file-handler=* /logging-profile=*/size-rotating-file-handler=* /logging-profile=*/socket-handler=* /periodic-size-rotating-file-handler=* /socket-handler=* {code} In HAL we use the metadata to validate user input and in this case, we undefine the alternative attribute the user didn't set, "filter", resulting in an error because the attribute doesn't exist. I did a workaround, but would be interesting to fix the alternatives metadata. > "filter-spec" attribute of socket-handler contains non existent "filter" alternative > ------------------------------------------------------------------------------------ > > Key: WFCORE-4042 > URL: https://issues.jboss.org/browse/WFCORE-4042 > Project: WildFly Core > Issue Type: Bug > Components: Logging > Reporter: Claudio Miranda > Assignee: James Perkins > > The socket-handler resource, contains an attribute "filter-spec" and the "alternatives" contains a non existent "filter" attribute > {code} > "filter-spec" => { > "type" => STRING, > "description" => "A filter expression value to define a filter. Example for a filter that does not match a pattern: not(match(\"JBAS.*\"))", > "expressions-allowed" => true, > "required" => false, > "nillable" => true, > "alternatives" => ["filter"], > "min-length" => 1L, > "max-length" => 2147483647L, > "access-type" => "read-write", > "storage" => "configuration", > "restart-required" => "no-services" > }, > {code} > I counted the following resources affected by the issue. > {code} > /logging-profile=*/async-handler=* > /logging-profile=*/console-handler=* > /logging-profile=*/custom-handler=* > /logging-profile=*/file-handler=* > /logging-profile=*/periodic-rotating-file-handler=* > /logging-profile=*/periodic-size-rotating-file-handler=* > /logging-profile=*/size-rotating-file-handler=* > /logging-profile=*/socket-handler=* > /logging-profile=*/root-logger=ROOT > /periodic-size-rotating-file-handler=* > /socket-handler=* > {code} > In HAL we use the metadata to validate user input and in this case, we undefine the alternative attribute the user didn't set, "filter", resulting in an error because the attribute doesn't exist. I did a workaround, but would be interesting to fix the alternatives metadata. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4042) "filter-spec" attribute of socket-handler contains non existent "filter" alternative

by Claudio Miranda (JIRA)

[ https://issues.jboss.org/browse/WFCORE-4042?page=com.atlassian.jira.plugi... ] Claudio Miranda updated WFCORE-4042: ------------------------------------ Description: The socket-handler resource, contains an attribute "filter-spec" and the "alternatives" contains a non existent "filter" attribute {code} "filter-spec" => { "type" => STRING, "description" => "A filter expression value to define a filter. Example for a filter that does not match a pattern: not(match(\"JBAS.*\"))", "expressions-allowed" => true, "required" => false, "nillable" => true, "alternatives" => ["filter"], "min-length" => 1L, "max-length" => 2147483647L, "access-type" => "read-write", "storage" => "configuration", "restart-required" => "no-services" }, {code} I counted the following resources affected by the issue. {code} /logging-profile=*/async-handler=* /logging-profile=*/console-handler=* /logging-profile=*/custom-handler=* /logging-profile=*/file-handler=* /logging-profile=*/periodic-rotating-file-handler=* /logging-profile=*/periodic-size-rotating-file-handler=* /logging-profile=*/size-rotating-file-handler=* /logging-profile=*/socket-handler=* /periodic-size-rotating-file-handler=* /socket-handler=* {code} In HAL we use the metadata to validate user input and in this case, we undefine the alternative attribute the user didn't set, "filter", resulting in an error because the attribute doesn't exist. I did a workaround, but would be interesting to fix the alternatives metadata. was: The socket-handler resource, contains an attribute "filter-spec" and the "alternatives" contains a non existent "filter" attribute {code} "filter-spec" => { "type" => STRING, "description" => "A filter expression value to define a filter. Example for a filter that does not match a pattern: not(match(\"JBAS.*\"))", "expressions-allowed" => true, "required" => false, "nillable" => true, "alternatives" => ["filter"], "min-length" => 1L, "max-length" => 2147483647L, "access-type" => "read-write", "storage" => "configuration", "restart-required" => "no-services" }, {code} In HAL we use the metadata to validate user input and in this case, we undefine the alternative attribute the user didn't set, "filter", resulting in an error because the attribute doesn't exist. I did a workaround, but would be interesting to fix the alternatives metadata. > "filter-spec" attribute of socket-handler contains non existent "filter" alternative > ------------------------------------------------------------------------------------ > > Key: WFCORE-4042 > URL: https://issues.jboss.org/browse/WFCORE-4042 > Project: WildFly Core > Issue Type: Bug > Components: Logging > Reporter: Claudio Miranda > Assignee: James Perkins > > The socket-handler resource, contains an attribute "filter-spec" and the "alternatives" contains a non existent "filter" attribute > {code} > "filter-spec" => { > "type" => STRING, > "description" => "A filter expression value to define a filter. Example for a filter that does not match a pattern: not(match(\"JBAS.*\"))", > "expressions-allowed" => true, > "required" => false, > "nillable" => true, > "alternatives" => ["filter"], > "min-length" => 1L, > "max-length" => 2147483647L, > "access-type" => "read-write", > "storage" => "configuration", > "restart-required" => "no-services" > }, > {code} > I counted the following resources affected by the issue. > {code} > /logging-profile=*/async-handler=* > /logging-profile=*/console-handler=* > /logging-profile=*/custom-handler=* > /logging-profile=*/file-handler=* > /logging-profile=*/periodic-rotating-file-handler=* > /logging-profile=*/periodic-size-rotating-file-handler=* > /logging-profile=*/size-rotating-file-handler=* > /logging-profile=*/socket-handler=* > /periodic-size-rotating-file-handler=* > /socket-handler=* > {code} > In HAL we use the metadata to validate user input and in this case, we undefine the alternative attribute the user didn't set, "filter", resulting in an error because the attribute doesn't exist. I did a workaround, but would be interesting to fix the alternatives metadata. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10871) Agroal: service name used for the DS/XADS should be driven by DATASOURCE_RUNTIME_CAPABILITY

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-10871?page=com.atlassian.jira.plugin... ] Brian Stansberry commented on WFLY-10871: ----------------------------------------- Something like this should do it, although I haven't tested this: https://github.com/wildfly/wildfly/compare/master...bstansberry:WFLY-10871 [~jamezp] expressed interest in adding a test of using an Agroal DS in batch-jberet, which would serve the purpose of validating that the service wiring is done correctly. Something in clustering (probably Infinispan) as well as messaging-activemq also can inject datasources via capabilities. > Agroal: service name used for the DS/XADS should be driven by DATASOURCE_RUNTIME_CAPABILITY > ------------------------------------------------------------------------------------------- > > Key: WFLY-10871 > URL: https://issues.jboss.org/browse/WFLY-10871 > Project: WildFly > Issue Type: Bug > Reporter: Martin Simka > Assignee: Luis Barreiro > Priority: Blocker > > item 11 from [Brian's review|https://github.com/wildfly/wildfly/pull/11176#issuecomment-413283172] > {quote} > The service name used for the DS/XADS is not correct. It needs to be driven by the DATASOURCE_RUNTIME_CAPABILITY, otherwise other subsystems cannot use the capability to access the service. > {quote} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-378) Random TAG is being generated on deploying from kiali/kiali

by Guilherme Baufaker Rêgo (JIRA)

[ https://issues.jboss.org/browse/SWSQE-378?page=com.atlassian.jira.plugin.... ] Guilherme Baufaker Rêgo reassigned SWSQE-378: --------------------------------------------- Assignee: Hayk Hovsepyan (was: Guilherme Baufaker Rêgo) Hayk, I have sent this fix http://git.app.eng.bos.redhat.com/git/kiali-qe-utils.git/commit/?id=958c8... Can you double check? > Random TAG is being generated on deploying from kiali/kiali > ----------------------------------------------------------- > > Key: SWSQE-378 > URL: https://issues.jboss.org/browse/SWSQE-378 > Project: Kiali QE > Issue Type: Bug > Reporter: Guilherme Baufaker Rêgo > Assignee: Hayk Hovsepyan > > The random tag was included because the images weren't been overridden, but when we are deploying from "kiali/kiali" the exactly tag should be matched > Example: Using Docker tag v0.6.0YWZk from Docker Repo docker.io/kiali/kiali from (http://jenkins2.bc.jonqe.lab.eng.bos.redhat.com:8080/job/Kiali-on-Openshi...) > YWZk is the random component. > This need to be switched when are using kialiqe/kiali -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2889) Research accessibility considerations for Data Type list drag-n-drop.

by Sarah Rambacher (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2889?page=com.atlassian.jira.plugi... ] Sarah Rambacher commented on DROOLS-2889: ----------------------------------------- Is it a fair assumption that an item cannot be dragged out of its nested list into a different nested list? E.g. in the attached screen shot, street, city name, or postal code *could* be re-ordered within tAddress, but *could not* be dragged up a level to tPerson or out to another item at the same level as tAddress? > Research accessibility considerations for Data Type list drag-n-drop. > ---------------------------------------------------------------------- > > Key: DROOLS-2889 > URL: https://issues.jboss.org/browse/DROOLS-2889 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Liz Clayton > Assignee: Sarah Rambacher > Labels: UX, UXTeam, drools-tools > Attachments: Screen Shot 2018-08-13 at 1.42.16 PM.png > > > Use Case: As a DMN user I will want to be able to reorder the list of Custom data types so that I can arrange data types in a logical order. > Notes: > * The Data Type dialog leverage the following PR list pattern: > https://www.patternfly.org/pattern-library/content-views/tree-list-view > * The list will need to be re-orderable, there is an open design jira to determine the interaction options for that feature. > * Design is currently being iterated upon, but last iteration wireframes are posted at: https://redhat.invisionapp.com/share/B7NEEUSV539 > Verification conditions: > * Research results summarized in the jira or a linked google doc., etc. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-378) Random TAG is being generated on deploying from kiali/kiali

by Matt Mahoney (JIRA)

[ https://issues.jboss.org/browse/SWSQE-378?page=com.atlassian.jira.plugin.... ] Matt Mahoney commented on SWSQE-378: ------------------------------------ [~gbaufake] kiali/kiali:<tag> seems to be working now. Thank you. Also, there is still a use case that we should consider for the kiali-qe/kiali:<tag> case: Build a tagged Kiali, and then deploy that tag to multiple OS configuration. Do not want always to build again just to deploy the same UI/Core versions to different OS conflagrations. > Random TAG is being generated on deploying from kiali/kiali > ----------------------------------------------------------- > > Key: SWSQE-378 > URL: https://issues.jboss.org/browse/SWSQE-378 > Project: Kiali QE > Issue Type: Bug > Reporter: Guilherme Baufaker Rêgo > Assignee: Guilherme Baufaker Rêgo > > The random tag was included because the images weren't been overridden, but when we are deploying from "kiali/kiali" the exactly tag should be matched > Example: Using Docker tag v0.6.0YWZk from Docker Repo docker.io/kiali/kiali from (http://jenkins2.bc.jonqe.lab.eng.bos.redhat.com:8080/job/Kiali-on-Openshi...) > YWZk is the random component. > This need to be switched when are using kialiqe/kiali -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10868) Agroal: DataSourceDefinitionDescriptorProcessor is missing i18n in some exception messages

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-10868?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFLY-10868: ------------------------------------ Fix Version/s: 14.0.0.CR1 > Agroal: DataSourceDefinitionDescriptorProcessor is missing i18n in some exception messages > ------------------------------------------------------------------------------------------ > > Key: WFLY-10868 > URL: https://issues.jboss.org/browse/WFLY-10868 > Project: WildFly > Issue Type: Bug > Reporter: Martin Simka > Assignee: Luis Barreiro > Priority: Blocker > Fix For: 14.0.0.CR1 > > > item 7 from [Brian's review|https://github.com/wildfly/wildfly/pull/11176#issuecomment-413283172] > {quote} > DataSourceDefinitionDescriptorProcessor is missing i18n in some exception messages > {quote} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10869) Agroal: AgroalSubsystemAdd.populateModel and AgroalSubsystemRemove should be removed

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-10869?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFLY-10869: ------------------------------------ Fix Version/s: 14.0.0.CR1 > Agroal: AgroalSubsystemAdd.populateModel and AgroalSubsystemRemove should be removed > ------------------------------------------------------------------------------------ > > Key: WFLY-10869 > URL: https://issues.jboss.org/browse/WFLY-10869 > Project: WildFly > Issue Type: Bug > Reporter: Martin Simka > Assignee: Luis Barreiro > Priority: Blocker > Fix For: 14.0.0.CR1 > > > items 8 and 9 from [Brian's review|https://github.com/wildfly/wildfly/pull/11176#issuecomment-413283172] > {quote} > 8. AgroalSubsystemAdd.populateModel should be removed > 9 .AgroalSubsystemRemove should be removed; use ReloadRequiredRemoveStepHandler > {quote} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10866) Agroal attributes are not properly described

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-10866?page=com.atlassian.jira.plugin... ] Brian Stansberry commented on WFLY-10866: ----------------------------------------- In both cases the attribute in question uses PrimitiveListAttributeDefinition. I believe 'statistics' should be ObjectTypeAttributeDefinition and class-info as PropertiesAttributeDefinition or SimpleMapAttributeDefinition. > Agroal attributes are not properly described > -------------------------------------------- > > Key: WFLY-10866 > URL: https://issues.jboss.org/browse/WFLY-10866 > Project: WildFly > Issue Type: Bug > Reporter: Martin Simka > Assignee: Luis Barreiro > Priority: Blocker > Fix For: 14.0.0.CR1 > > > item 1 from [Brian's review|https://github.com/wildfly/wildfly/pull/11176#issuecomment-413283172] > {quote} > The DS/XADS 'statistics' attribute is not properly described. It has a static set of response fields and the value of each field has a known type, nillability etc. > {quote} > item 6 from [Brian's review|https://github.com/wildfly/wildfly/pull/11176#issuecomment-413283172] > {quote} > The class-info attribute on the driver is not properly described. It's a map of property name -> single param name, not a primitive list. > {quote} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10866) Agroal attributes are not properly described

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-10866?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFLY-10866: ------------------------------------ Fix Version/s: 14.0.0.CR1 > Agroal attributes are not properly described > -------------------------------------------- > > Key: WFLY-10866 > URL: https://issues.jboss.org/browse/WFLY-10866 > Project: WildFly > Issue Type: Bug > Reporter: Martin Simka > Assignee: Luis Barreiro > Priority: Blocker > Fix For: 14.0.0.CR1 > > > item 1 from [Brian's review|https://github.com/wildfly/wildfly/pull/11176#issuecomment-413283172] > {quote} > The DS/XADS 'statistics' attribute is not properly described. It has a static set of response fields and the value of each field has a known type, nillability etc. > {quote} > item 6 from [Brian's review|https://github.com/wildfly/wildfly/pull/11176#issuecomment-413283172] > {quote} > The class-info attribute on the driver is not properly described. It's a map of property name -> single param name, not a primitive list. > {quote} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 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 August 2018