September 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-4778) [DMN Designer] Multiple DRDs Support (Backlog)

by Guilherme Gomes (Jira)

[ https://issues.redhat.com/browse/DROOLS-4778?page=com.atlassian.jira.plug... ] Guilherme Gomes closed DROOLS-4778. ----------------------------------- Resolution: Duplicate Issue This JIRa is being closed in favor https://issues.redhat.com/browse/KOGITO-3020. > [DMN Designer] Multiple DRDs Support (Backlog) > ---------------------------------------------- > > Key: DROOLS-4778 > URL: https://issues.redhat.com/browse/DROOLS-4778 > Project: Drools > Issue Type: Epic > Components: DMN Editor > Reporter: Guilherme Gomes > Assignee: Guilherme Gomes > Priority: Major > Labels: drools-tools > > This is an umbrella for all JIRAs related to the Multiple DRDs Support feature. -- This message was sent by Atlassian Jira (v7.13.8#713008)

3 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4779) [DMN Designer] Multiple DRDs Support - Show an interaction icon when users select more than one DMN element

by Guilherme Gomes (Jira)

[ https://issues.redhat.com/browse/DROOLS-4779?page=com.atlassian.jira.plug... ] Guilherme Gomes closed DROOLS-4779. ----------------------------------- Resolution: Duplicate Issue This issue will be addressed by https://issues.redhat.com/browse/KOGITO-2673. > [DMN Designer] Multiple DRDs Support - Show an interaction icon when users select more than one DMN element > ----------------------------------------------------------------------------------------------------------- > > Key: DROOLS-4779 > URL: https://issues.redhat.com/browse/DROOLS-4779 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Guilherme Gomes > Assignee: Daniel José dos Santos > Priority: Major > Labels: drools-tools > Attachments: demo.gif, prototype1.png > > > When users select more than one DMN element: > !demo.gif|width=300! > We must display an interaction icon, like this one: > !prototype1.png|width=300! > ⚠️ Notice: > - The correct icon is the **sitemap** https://fontawesome.com/icons/sitemap?style=solid, https://issues.jboss.org/browse/DROOLS-3566?focusedCommentId=13804999&pag... > - We shouldn't show the icon when the selection has only one element (since we will have the **sitemap** icon for individual nodes) > - This JIRA doesn't comprehends any action. The interaction with this icon will be covered by DROOLS-4781 -- This message was sent by Atlassian Jira (v7.13.8#713008)

3 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4781) [DMN Designer] Multiple DRDs Support - Show DRDs action flyout menu for DRD selection

by Guilherme Gomes (Jira)

[ https://issues.redhat.com/browse/DROOLS-4781?page=com.atlassian.jira.plug... ] Guilherme Gomes closed DROOLS-4781. ----------------------------------- Resolution: Duplicate Issue This issue was fixed by https://issues.redhat.com/browse/KOGITO-2664. > [DMN Designer] Multiple DRDs Support - Show DRDs action flyout menu for DRD selection > ------------------------------------------------------------------------------------- > > Key: DROOLS-4781 > URL: https://issues.redhat.com/browse/DROOLS-4781 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Guilherme Gomes > Assignee: Daniel José dos Santos > Priority: Major > Labels: drools-tools > Attachments: prototype3.png > > > Show DRDs action flyout menu for DRD selection: > !prototype3.png|width=600! > ⚠️ Notice: > - *Before starting this JIRA*, check with [~uxdlc] which action triggers this menu (right click, single click, etc), and revisit the icons (added be DROOLS-4780 and DROOLS-4779) to add the action that will trigger this flyout menu -- This message was sent by Atlassian Jira (v7.13.8#713008)

3 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4780) [DMN Designer] Multiple DRDs Support - Show a new action icon when users select one DMN element

by Guilherme Gomes (Jira)

[ https://issues.redhat.com/browse/DROOLS-4780?page=com.atlassian.jira.plug... ] Guilherme Gomes closed DROOLS-4780. ----------------------------------- Resolution: Duplicate Issue This issue was fixed by https://issues.redhat.com/browse/KOGITO-2664. > [DMN Designer] Multiple DRDs Support - Show a new action icon when users select one DMN element > ----------------------------------------------------------------------------------------------- > > Key: DROOLS-4780 > URL: https://issues.redhat.com/browse/DROOLS-4780 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Guilherme Gomes > Assignee: Daniel José dos Santos > Priority: Major > Labels: drools-tools > Attachments: prototype2.png > > > When users select one DMN element, an interaction a new action icon must be displayed: > !prototype2.png|width=600! > ⚠️ Notice: > - The correct icon is the **sitemap** https://fontawesome.com/icons/sitemap?style=solid, https://issues.jboss.org/browse/DROOLS-3566?focusedCommentId=13804999&pag... > - This JIRA doesn't comprehends any action. The interaction with this icon will be covered by DROOLS-4781 -- This message was sent by Atlassian Jira (v7.13.8#713008)

3 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-5143) Bouncycastle - Failing tests in RESTEasy TS

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFCORE-5143?page=com.atlassian.jira.plug... ] Brian Stansberry commented on WFCORE-5143: ------------------------------------------ Thanks, [~dlofthouse]. We need to be more careful when it comes to projects that base on WildFly; the meaning of 'jboss-api=private' is not clear cut at all there. Note the module isn't removed; it's just not provisioned. Sounds like it needs to be though. > Bouncycastle - Failing tests in RESTEasy TS > ------------------------------------------- > > Key: WFCORE-5143 > URL: https://issues.redhat.com/browse/WFCORE-5143 > Project: WildFly Core > Issue Type: Bug > Components: Security > Affects Versions: 13.0.0.Beta6 > Reporter: Emmanuel Hugonnet > Assignee: Emmanuel Hugonnet > Priority: Blocker > > [~ehugonnet] please set the component. I cannot find anything suitable. > I noticed it in the context of a bootable JAR execution but [~jfdenise] confirmed this happens with WF 21 Beta1. > 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 [2]) but fail against 21.0.0.Beta1, so it is a regression. > There are 108 tests failing but this JIRA is reporting just one as a reference, see "Steps to reproduce" in order to have a full list: > {code} > org.jboss.resteasy.test.providers.mediatype.BlacklistedMediaTypeTest.org.jboss.resteasy.test.providers.mediatype.BlacklistedMediaTypeTest > Error Details > Cannot deploy BlacklistedMediaTypeTest.war: {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-1" => {"WFLYCTL0080: Failed services" => {"jboss.module.service.\"deployment.BlacklistedMediaTypeTest.war\".main" => "WFLYSRV0179: Failed to load module: deployment.BlacklistedMediaTypeTest.war > Caused by: org.jboss.modules.ModuleNotFoundException: org.bouncycastle"}}}} > {code} > *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.repo.local=/home/my-local-repo > {code} > 3. cd to testsuite directory: > {code} > cd testsuite > {code} > 4. run the test against WF 21.0.0.Beta1 with bootable JAR: > {code} > mvn clean verify -am -pl integration-tests -Dmaven.repo.local=/home/my-local-repo -Dserver.version=21.0.0.Beta1 -Dtest=org.jboss.resteasy.test.providers.mediatype.BlacklistedMediaTypeTest -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.repo.local=/home/my-local-repo -Dserver.version=20.0.1.Final -Dtest=org.jboss.resteasy.test.providers.mediatype.BlacklistedMediaTypeTest -Ddisable.microprofile.tests -Dserver.home=foo -Dts.bootable > {code} > The test should *pass* > [1] > https://github.com/resteasy/Resteasy/pull/2526/files#diff-8c7ea03eb619e46... > [2] > https://github.com/resteasy/Resteasy/pull/2526/files#diff-8c7ea03eb619e46... -- This message was sent by Atlassian Jira (v7.13.8#713008)

3 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-5143) Bouncycastle - Failing tests in RESTEasy TS

by Darran Lofthouse (Jira)

[ https://issues.redhat.com/browse/WFCORE-5143?page=com.atlassian.jira.plug... ] Darran Lofthouse commented on WFCORE-5143: ------------------------------------------ FYI KeyCloak has a direct dependency on org.bouncycastle from their adaptor feature pack so we should be cautious about removing this module. > Bouncycastle - Failing tests in RESTEasy TS > ------------------------------------------- > > Key: WFCORE-5143 > URL: https://issues.redhat.com/browse/WFCORE-5143 > Project: WildFly Core > Issue Type: Bug > Components: Security > Affects Versions: 13.0.0.Beta6 > Reporter: Emmanuel Hugonnet > Assignee: Emmanuel Hugonnet > Priority: Blocker > > [~ehugonnet] please set the component. I cannot find anything suitable. > I noticed it in the context of a bootable JAR execution but [~jfdenise] confirmed this happens with WF 21 Beta1. > 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 [2]) but fail against 21.0.0.Beta1, so it is a regression. > There are 108 tests failing but this JIRA is reporting just one as a reference, see "Steps to reproduce" in order to have a full list: > {code} > org.jboss.resteasy.test.providers.mediatype.BlacklistedMediaTypeTest.org.jboss.resteasy.test.providers.mediatype.BlacklistedMediaTypeTest > Error Details > Cannot deploy BlacklistedMediaTypeTest.war: {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-1" => {"WFLYCTL0080: Failed services" => {"jboss.module.service.\"deployment.BlacklistedMediaTypeTest.war\".main" => "WFLYSRV0179: Failed to load module: deployment.BlacklistedMediaTypeTest.war > Caused by: org.jboss.modules.ModuleNotFoundException: org.bouncycastle"}}}} > {code} > *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.repo.local=/home/my-local-repo > {code} > 3. cd to testsuite directory: > {code} > cd testsuite > {code} > 4. run the test against WF 21.0.0.Beta1 with bootable JAR: > {code} > mvn clean verify -am -pl integration-tests -Dmaven.repo.local=/home/my-local-repo -Dserver.version=21.0.0.Beta1 -Dtest=org.jboss.resteasy.test.providers.mediatype.BlacklistedMediaTypeTest -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.repo.local=/home/my-local-repo -Dserver.version=20.0.1.Final -Dtest=org.jboss.resteasy.test.providers.mediatype.BlacklistedMediaTypeTest -Ddisable.microprofile.tests -Dserver.home=foo -Dts.bootable > {code} > The test should *pass* > [1] > https://github.com/resteasy/Resteasy/pull/2526/files#diff-8c7ea03eb619e46... > [2] > https://github.com/resteasy/Resteasy/pull/2526/files#diff-8c7ea03eb619e46... -- This message was sent by Atlassian Jira (v7.13.8#713008)

3 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-5143) Bouncycastle - Failing tests in RESTEasy TS

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFCORE-5143?page=com.atlassian.jira.plug... ] Brian Stansberry commented on WFCORE-5143: ------------------------------------------ [~ehugonnet] [~fburzigo] [~rsigal] [~asoldano] Note that this relies on unsupported behavior: https://github.com/resteasy/Resteasy/blob/master/testsuite/integration-te... The org.bouncycastle module is private and we can remove it at any time. We shouldn't in a micro release but can in a major/minor. I don't think we are obligated to provision it in a slimmed server. If we can provision it without doing things that are too ugly, that might be fine, but this test app should package bouncycastle itself if it needs it. > Bouncycastle - Failing tests in RESTEasy TS > ------------------------------------------- > > Key: WFCORE-5143 > URL: https://issues.redhat.com/browse/WFCORE-5143 > Project: WildFly Core > Issue Type: Bug > Components: Security > Affects Versions: 13.0.0.Beta6 > Reporter: Emmanuel Hugonnet > Assignee: Emmanuel Hugonnet > Priority: Blocker > > [~ehugonnet] please set the component. I cannot find anything suitable. > I noticed it in the context of a bootable JAR execution but [~jfdenise] confirmed this happens with WF 21 Beta1. > 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 [2]) but fail against 21.0.0.Beta1, so it is a regression. > There are 108 tests failing but this JIRA is reporting just one as a reference, see "Steps to reproduce" in order to have a full list: > {code} > org.jboss.resteasy.test.providers.mediatype.BlacklistedMediaTypeTest.org.jboss.resteasy.test.providers.mediatype.BlacklistedMediaTypeTest > Error Details > Cannot deploy BlacklistedMediaTypeTest.war: {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-1" => {"WFLYCTL0080: Failed services" => {"jboss.module.service.\"deployment.BlacklistedMediaTypeTest.war\".main" => "WFLYSRV0179: Failed to load module: deployment.BlacklistedMediaTypeTest.war > Caused by: org.jboss.modules.ModuleNotFoundException: org.bouncycastle"}}}} > {code} > *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.repo.local=/home/my-local-repo > {code} > 3. cd to testsuite directory: > {code} > cd testsuite > {code} > 4. run the test against WF 21.0.0.Beta1 with bootable JAR: > {code} > mvn clean verify -am -pl integration-tests -Dmaven.repo.local=/home/my-local-repo -Dserver.version=21.0.0.Beta1 -Dtest=org.jboss.resteasy.test.providers.mediatype.BlacklistedMediaTypeTest -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.repo.local=/home/my-local-repo -Dserver.version=20.0.1.Final -Dtest=org.jboss.resteasy.test.providers.mediatype.BlacklistedMediaTypeTest -Ddisable.microprofile.tests -Dserver.home=foo -Dts.bootable > {code} > The test should *pass* > [1] > https://github.com/resteasy/Resteasy/pull/2526/files#diff-8c7ea03eb619e46... > [2] > https://github.com/resteasy/Resteasy/pull/2526/files#diff-8c7ea03eb619e46... -- This message was sent by Atlassian Jira (v7.13.8#713008)

3 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2502) If the KUBERNETES_NAMESPACE is not set the default value is the "default" namespace

by Sebastian Laskawiec (Jira)

[ https://issues.redhat.com/browse/JGRP-2502?page=com.atlassian.jira.plugin... ] Sebastian Laskawiec commented on JGRP-2502: ------------------------------------------- [~filippe.spolti] oooh, I'm not a maintainer of OpenShift PING. Please reach out the maintainers of that project and ask them directly. > If the KUBERNETES_NAMESPACE is not set the default value is the "default" namespace > ------------------------------------------------------------------------------------ > > Key: JGRP-2502 > URL: https://issues.redhat.com/browse/JGRP-2502 > Project: JGroups > Issue Type: Bug > Affects Versions: 5.0.4 > Reporter: Filippe Spolti > Assignee: Sebastian Laskawiec > Priority: Minor > > If no namespace is set it defaults to the "default" ocp namespace which will case the warn as described in the log message below: > > {code:java} > WARN [org.jgroups.protocols.kubernetes.KUBE_PING] (thread-9,ee,hdm78-kieserver-1-nggcf) failed getting JSON response from Kubernetes Client[masterUrl=https://172.30.0.1:443/api/v1, headers={Authorization=#MASKED:937#}, connectTimeout=5000, readTimeout=30000, operationAttempts=3, operationSleep=1000, streamProvider=org.jgroups.protocols.kubernetes.stream.TokenStreamProvider@69991c01] for cluster [ee], namespace [default], labels [null]; encountered [java.lang.Exception: 3 attempt(s) with a 1000ms sleep to execute [OpenStream] failed. Last failure was [java.io.IOException: Server returned HTTP response code: 403 for URL: https://172.30.0.1:443/api/v1/namespaces/default/pods]] > {code} > IMHO the default namespace should not be used in this case since this namespace should not be used to deploy applications. > > If the namespace is not set it means that we do not want to enable the clustering feature, as the namespace is set if the namespace is not set, this condition [1] is not satisfied and the configuration will proceed. > > Another problem found in the tests is that, if we do set the KUBERNETES_NAMESPACE with no value, it will detect that the env has an value and will try to use a blank namespace: > > {code:java} > failed getting JSON response from Kubernetes Client[masterUrl=https://172.30.0.1:443/api/v1 , headers={Authorization=#MASKED:874#}, connectTimeout=5000, readTimeout=30000, operationAttempts=3, operationSleep=1000, streamProvider=org.jgroups.protocols.kubernetes.stream.TokenStreamProvider@17978314] for cluster [ee], namespace [], labels [null]; encountered [java.lang.Exception: 3 attempt(s) with a 1000ms sleep to execute [OpenStream] failed. Last failure was [java.io.IOException: Server returned HTTP response code: 403 for URL: https://172.30.0.1:443/api/v1/pods ]] > {code} > > [1] - https://github.com/jgroups-extras/jgroups-kubernetes/blob/master/src/main/java/org/jgroups/protocols/kubernetes/KUBE_PING.java#L145 > -- This message was sent by Atlassian Jira (v7.13.8#713008)

3 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2502) If the KUBERNETES_NAMESPACE is not set the default value is the "default" namespace

by Filippe Spolti (Jira)

[ https://issues.redhat.com/browse/JGRP-2502?page=com.atlassian.jira.plugin... ] Filippe Spolti commented on JGRP-2502: -------------------------------------- no asking about keycloak, just asking to have the same behavior than openshift.PING where we could disable clustering if no envs set. > If the KUBERNETES_NAMESPACE is not set the default value is the "default" namespace > ------------------------------------------------------------------------------------ > > Key: JGRP-2502 > URL: https://issues.redhat.com/browse/JGRP-2502 > Project: JGroups > Issue Type: Bug > Affects Versions: 5.0.4 > Reporter: Filippe Spolti > Assignee: Sebastian Laskawiec > Priority: Minor > > If no namespace is set it defaults to the "default" ocp namespace which will case the warn as described in the log message below: > > {code:java} > WARN [org.jgroups.protocols.kubernetes.KUBE_PING] (thread-9,ee,hdm78-kieserver-1-nggcf) failed getting JSON response from Kubernetes Client[masterUrl=https://172.30.0.1:443/api/v1, headers={Authorization=#MASKED:937#}, connectTimeout=5000, readTimeout=30000, operationAttempts=3, operationSleep=1000, streamProvider=org.jgroups.protocols.kubernetes.stream.TokenStreamProvider@69991c01] for cluster [ee], namespace [default], labels [null]; encountered [java.lang.Exception: 3 attempt(s) with a 1000ms sleep to execute [OpenStream] failed. Last failure was [java.io.IOException: Server returned HTTP response code: 403 for URL: https://172.30.0.1:443/api/v1/namespaces/default/pods]] > {code} > IMHO the default namespace should not be used in this case since this namespace should not be used to deploy applications. > > If the namespace is not set it means that we do not want to enable the clustering feature, as the namespace is set if the namespace is not set, this condition [1] is not satisfied and the configuration will proceed. > > Another problem found in the tests is that, if we do set the KUBERNETES_NAMESPACE with no value, it will detect that the env has an value and will try to use a blank namespace: > > {code:java} > failed getting JSON response from Kubernetes Client[masterUrl=https://172.30.0.1:443/api/v1 , headers={Authorization=#MASKED:874#}, connectTimeout=5000, readTimeout=30000, operationAttempts=3, operationSleep=1000, streamProvider=org.jgroups.protocols.kubernetes.stream.TokenStreamProvider@17978314] for cluster [ee], namespace [], labels [null]; encountered [java.lang.Exception: 3 attempt(s) with a 1000ms sleep to execute [OpenStream] failed. Last failure was [java.io.IOException: Server returned HTTP response code: 403 for URL: https://172.30.0.1:443/api/v1/pods ]] > {code} > > [1] - https://github.com/jgroups-extras/jgroups-kubernetes/blob/master/src/main/java/org/jgroups/protocols/kubernetes/KUBE_PING.java#L145 > -- This message was sent by Atlassian Jira (v7.13.8#713008)

3 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5624) It should be possible to escape the build popup

by Toni Rikkola (Jira)

[ https://issues.redhat.com/browse/DROOLS-5624?page=com.atlassian.jira.plug... ] Toni Rikkola updated DROOLS-5624: --------------------------------- Sprint: 2020 Week 37-39 (from Sep 7) (was: 2020 Week 37-39 (from Sep 7), 2020 Week 40-42 (from Sep 28)) > It should be possible to escape the build popup > ----------------------------------------------- > > Key: DROOLS-5624 > URL: https://issues.redhat.com/browse/DROOLS-5624 > Project: Drools > Issue Type: Feature Request > Reporter: Toni Rikkola > Assignee: Toni Rikkola > Priority: Major > Labels: drools-tools > > The build can take 1, 5 or 60 minutes. UI should not block you from using the workbench during this time. -- This message was sent by Atlassian Jira (v7.13.8#713008)

3 years, 8 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 September 2020