July 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFWIP-167) EAP Operator handling ConfigMap internally

by Jeff Mesnil (Jira)

[ https://issues.jboss.org/browse/WFWIP-167?page=com.atlassian.jira.plugin.... ] Jeff Mesnil commented on WFWIP-167: ----------------------------------- The ConfigMap is the standard way to provide configuration to Kubernetes application and is well suited for this feature. Having a file that must be accessible to the operator pod would be more complex to setup and less secure. This should be considered as an advanced feature and should only be used if the provided standalone configuration can not match the application requirements with all the caveats you mention (ConfigMap are not immutable). > EAP Operator handling ConfigMap internally > ------------------------------------------ > > Key: WFWIP-167 > URL: https://issues.jboss.org/browse/WFWIP-167 > Project: WildFly WIP > Issue Type: Bug > Components: OpenShift > Reporter: Martin Choma > Assignee: Jeff Mesnil > Priority: Major > > If I understand description in [1] correctly. To specify custom standalone.xml I have to create ConfigMap with standalone.xml first and afterwards link operator to this ConfigMap. > Is it possible to handle creation of ConfigMap and storing standalone.xml for me? Ideally I just specify file URI where custom standalone.xml is located. This location have to be accessible from operator pod. In this way we can look at it as hiding internals (implementation details) from users. > Currently when user wants to change standalone.xml he does in ConfigMap, not operator. When changing standalone.xml through config map, I assume pod have to be restarted manually. Operator could do that for me. > However this can be triggered by storing newer version of standalone.xml under another key, eg `standalone.xml.v2` and changing `StandaloneConfigMapSpec.key` in operator. > What do you think? Have you considered this approach? > [1] https://github.com/wildfly/wildfly-operator/blob/master/doc/apis.adoc#sta... -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4328) [DMN Designer] Search feature - Header is not being indexed

by Guilherme Gomes (Jira)

[ https://issues.jboss.org/browse/DROOLS-4328?page=com.atlassian.jira.plugi... ] Guilherme Gomes updated DROOLS-4328: ------------------------------------ Description: Grid Header cells are not being indexed. It might be nice to be able to search on these too. This JIRA was generated by this comment: https://github.com/kiegroup/kie-wb-common/pull/2749#pullrequestreview-262... Notice: https://github.com/kiegroup/kie-wb-common/pull/2785#issuecomment-516372530 (this issue happens into DMN boxed expressions too). was: Grid Header cells are not being indexed. It might be nice to be able to search on these too. This JIRA was generated by this comment: https://github.com/kiegroup/kie-wb-common/pull/2749#pullrequestreview-262... > [DMN Designer] Search feature - Header is not being indexed > ----------------------------------------------------------- > > Key: DROOLS-4328 > URL: https://issues.jboss.org/browse/DROOLS-4328 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Reporter: Guilherme Gomes > Assignee: Guilherme Gomes > Priority: Major > Labels: drools-tools > > Grid Header cells are not being indexed. It might be nice to be able to search on these too. > This JIRA was generated by this comment: https://github.com/kiegroup/kie-wb-common/pull/2749#pullrequestreview-262... > Notice: https://github.com/kiegroup/kie-wb-common/pull/2785#issuecomment-516372530 (this issue happens into DMN boxed expressions too). -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4328) [DMN Designer] Search feature - Header is not being indexed

by Guilherme Gomes (Jira)

[ https://issues.jboss.org/browse/DROOLS-4328?page=com.atlassian.jira.plugi... ] Guilherme Gomes updated DROOLS-4328: ------------------------------------ Story Points: 5 (was: 2) > [DMN Designer] Search feature - Header is not being indexed > ----------------------------------------------------------- > > Key: DROOLS-4328 > URL: https://issues.jboss.org/browse/DROOLS-4328 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Reporter: Guilherme Gomes > Assignee: Guilherme Gomes > Priority: Major > Labels: drools-tools > > Grid Header cells are not being indexed. It might be nice to be able to search on these too. > This JIRA was generated by this comment: https://github.com/kiegroup/kie-wb-common/pull/2749#pullrequestreview-262... -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4383) DMN DT exec model does not cascade down allowedValues to input/outputValues of DT

by Matteo Mortari (Jira)

Matteo Mortari created DROOLS-4383: -------------------------------------- Summary: DMN DT exec model does not cascade down allowedValues to input/outputValues of DT Key: DROOLS-4383 URL: https://issues.jboss.org/browse/DROOLS-4383 Project: Drools Issue Type: Task Components: dmn engine Reporter: Matteo Mortari Assignee: Matteo Mortari See [DROOLS-4379] test case a. To be investigated. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4525) Fix failing tests on IBM JDK

by James Perkins (Jira)

[ https://issues.jboss.org/browse/WFCORE-4525?page=com.atlassian.jira.plugi... ] James Perkins commented on WFCORE-4525: --------------------------------------- [~ropalka] Sorry yeah only the {{SilentModeTestCase}} now passes. I did start looking at the other two failures, I just haven't had time to really dig on. What it looks like is the wrong log context is being used. There might be a simple workaround for it, I just need to find time to test it. Maybe I'll get some time today if it's as simple as I think it might be. > Fix failing tests on IBM JDK > ---------------------------- > > Key: WFCORE-4525 > URL: https://issues.jboss.org/browse/WFCORE-4525 > Project: WildFly Core > Issue Type: Bug > Components: Logging > Reporter: Richard Opalka > Assignee: James Perkins > Priority: Major > Attachments: forked-booter.png, ibm-jdk8.png, oracle-jdk.png > > > The following tests are failing on latest IBM JDK 8: > --- > # testsuite/standalone > SilentModeTestCase > # testsuite/manualmode > CLIEmbedHostControllerTestCase > CLIEmbedServerTestCase > --- > Tested on: > --- > java version "1.8.0_211" > Java(TM) SE Runtime Environment (build 8.0.5.36 - pxa6480sr5fp36-20190510_01(SR5 FP36)) > IBM J9 VM (build 2.9, JRE 1.8.0 Linux amd64-64-Bit Compressed References 20190502_415899 (JIT enabled, AOT enabled) > OpenJ9 - 46e57f9 > OMR - 06a046a > IBM - 0b909bf) > JCL - 20190409_01 based on Oracle jdk8u211-b25 > --- -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-902) Investigate why Red Hat Tutorial is not working with Maistra 0.12.0

by Guilherme Baufaker Rêgo (Jira)

[ https://issues.jboss.org/browse/SWSQE-902?page=com.atlassian.jira.plugin.... ] Guilherme Baufaker Rêgo updated SWSQE-902: ------------------------------------------ Issue Type: Dev Task (was: QE Task) > Investigate why Red Hat Tutorial is not working with Maistra 0.12.0 > ------------------------------------------------------------------- > > Key: SWSQE-902 > URL: https://issues.jboss.org/browse/SWSQE-902 > Project: Kiali QE > Issue Type: Dev Task > Reporter: Guilherme Baufaker Rêgo > Priority: Major > > It seems readinessProbe/LivenessProbes might be causing issues with maistra 0.12.0 -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-902) Investigate why Red Hat Tutorial is not working with Maistra 0.12.0

by Guilherme Baufaker Rêgo (Jira)

[ https://issues.jboss.org/browse/SWSQE-902?page=com.atlassian.jira.plugin.... ] Guilherme Baufaker Rêgo reassigned SWSQE-902: --------------------------------------------- Assignee: Guilherme Baufaker Rêgo > Investigate why Red Hat Tutorial is not working with Maistra 0.12.0 > ------------------------------------------------------------------- > > Key: SWSQE-902 > URL: https://issues.jboss.org/browse/SWSQE-902 > Project: Kiali QE > Issue Type: Dev Task > Reporter: Guilherme Baufaker Rêgo > Assignee: Guilherme Baufaker Rêgo > Priority: Major > > It seems readinessProbe/LivenessProbes might be causing issues with maistra 0.12.0 -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-902) Investigate why Red Hat Tutorial is not working with Maistra 0.12.0

by Guilherme Baufaker Rêgo (Jira)

[ https://issues.jboss.org/browse/SWSQE-902?page=com.atlassian.jira.plugin.... ] Guilherme Baufaker Rêgo updated SWSQE-902: ------------------------------------------ Issue Type: QE Task (was: Dev Task) > Investigate why Red Hat Tutorial is not working with Maistra 0.12.0 > ------------------------------------------------------------------- > > Key: SWSQE-902 > URL: https://issues.jboss.org/browse/SWSQE-902 > Project: Kiali QE > Issue Type: QE Task > Reporter: Guilherme Baufaker Rêgo > Assignee: Guilherme Baufaker Rêgo > Priority: Major > > It seems readinessProbe/LivenessProbes might be causing issues with maistra 0.12.0 -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-902) Investigate why Red Hat Tutorial is not working with Maistra 0.12.0

by Guilherme Baufaker Rêgo (Jira)

Guilherme Baufaker Rêgo created SWSQE-902: --------------------------------------------- Summary: Investigate why Red Hat Tutorial is not working with Maistra 0.12.0 Key: SWSQE-902 URL: https://issues.jboss.org/browse/SWSQE-902 Project: Kiali QE Issue Type: QE Task Reporter: Guilherme Baufaker Rêgo It seems readinessProbe/LivenessProbes might be causing issues with maistra 0.12.0 -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3784) Increase the advanced user productivity when he creates a new Data Type

by Elizabeth Clayton (Jira)

[ https://issues.jboss.org/browse/DROOLS-3784?page=com.atlassian.jira.plugi... ] Elizabeth Clayton resolved DROOLS-3784. --------------------------------------- Resolution: Done Resolved per: https://issues.jboss.org/browse/DROOLS-4205 Note: The followup usability study will test the designs, unresolved issues will be filed as new jiras. > Increase the advanced user productivity when he creates a new Data Type > ----------------------------------------------------------------------- > > Key: DROOLS-3784 > URL: https://issues.jboss.org/browse/DROOLS-3784 > Project: Drools > Issue Type: Sub-task > Components: DMN Editor > Affects Versions: 7.18.0.Final > Reporter: Donato Marrazzo > Assignee: Elizabeth Clayton > Priority: Minor > Labels: Field, UX, UXTeam, drools-tools > Attachments: DT_List1.png, DT_List1b.png, Screenshot from 2019-03-25 15-27-51.png, constraints.png, nested.png, type-selector.png > > > The Data Type editor could be improved in terms of productivity and usability. > Ideally, the user should be able to create a complex type minimizing the mouse usage. > 1) Saving the node is an overhead for basic data type (e.g. age: number) > 2) Some actions in the kebab menu should be more visible and available even before saving the type (as standalone icon / buttons). Especially, insert nested, delete. > 3) Select type in the selector by typing the name of the type (see screenshot): it already works but it consider just the first letter typed. Since, by convention, all custom types starts with `t` letter, it would be better consider at least 2 letters. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 2 months

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 July 2019