February 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-1258) Powershell scripts should be signed

by Marek Kopecký (Jira)

[ https://issues.jboss.org/browse/WFCORE-1258?page=com.atlassian.jira.plugi... ] Marek Kopecký updated WFCORE-1258: ---------------------------------- Affects Version/s: 8.0.0.Beta5 > Powershell scripts should be signed > ----------------------------------- > > Key: WFCORE-1258 > URL: https://issues.jboss.org/browse/WFCORE-1258 > Project: WildFly Core > Issue Type: Task > Components: Scripts > Affects Versions: 2.0.5.Final, 8.0.0.Beta5 > Reporter: Tomaz Cerar > Priority: Major > > *.ps1 scripts should be signed otherwise uses would need to run in unsigned execution mode to make it work. > Scripts should work OOTB with RemoteSigned powershell execution policy -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3818) Improved console color capability detection

by Marek Kopecký (Jira)

[ https://issues.jboss.org/browse/WFCORE-3818?page=com.atlassian.jira.plugi... ] Marek Kopecký updated WFCORE-3818: ---------------------------------- Affects Version/s: 8.0.0.Beta5 > Improved console color capability detection > ------------------------------------------- > > Key: WFCORE-3818 > URL: https://issues.jboss.org/browse/WFCORE-3818 > Project: WildFly Core > Issue Type: Enhancement > Components: Logging, Scripts > Affects Versions: 8.0.0.Beta5 > Reporter: David Lloyd > Priority: Major > > We should improve on our ability to correctly detect color capabilities on the console. Many times, build logs in CI environments and similar cases are hard to read due to ANSI codes being written to a console that did not have color capabilities, and this could have been detected. > In the bash scripts, logic like the following can be used: > * If the {{tput}} command does not exist, fall back to checking {{TERM}}. > * If {{tput colors}} returns 8, 16, or 256, the terminal supports at least that many colors. > * The {{TERM}} var: the terminal supports 256 colors if {{TERM}} contains values xterm-256color, screen-256color, or generally any value containing 256 probably indicates color support. > * Check the value of the COLORTERM environment variable; if truecolor or 24bit, then you have 24-bit RGB capability (this should apply to Linux, Mac OS X, and Windows). > On Windows, COLORTERM is also usually supported in terminals supporting 24-bit RGB; presence of this env var may be sufficient to enable color. The TERM environment variable is also often supported. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11682) Clustered SLSB membership anomalies when all cluster members removed

by Jörg Bäsner (Jira)

[ https://issues.jboss.org/browse/WFLY-11682?page=com.atlassian.jira.plugin... ] Jörg Bäsner updated WFLY-11682: ------------------------------- > Clustered SLSB membership anomalies when all cluster members removed > -------------------------------------------------------------------- > > Key: WFLY-11682 > URL: https://issues.jboss.org/browse/WFLY-11682 > Project: WildFly > Issue Type: Bug > Components: Clustering, EJB > Affects Versions: 15.0.1.Final > Environment: WildFly running in an n-node cluster with an EJB client sending requests even during the time the cluster is down. > Reporter: Jörg Bäsner > Assignee: Richard Achmatowicz > Priority: Major > Attachments: node1.txt, node12.txt, node2.txt, node3.txt, playground.zip > > > This description will be based on a 3 node cluster. Cluster node 1 and 2 are configured in the {{PROVIDER_URL}}, node 3 is not. > The client has a custom ClusterNodeSelector implementation that is printing the {{connectedNodes}} and the {{availableNodes}} and doing a random balancing. > As long as all nodes are up and running the client is calling EJBs in a balanced way. > When node1 is shut down, the client get the notification below: > {code}... > DEBUG (XNIO-1 task-1) [org.jboss.ejb.client.invocation] Received MODULE_UNAVAILABLE(9) message for module /playground > DEBUG (XNIO-1 task-4) [org.jboss.ejb.client.invocation] Received MODULE_UNAVAILABLE(9) message for module /playground > DEBUG (XNIO-1 task-4) [org.jboss.ejb.client.invocation] Received MODULE_UNAVAILABLE(9) message for module /playground > DEBUG (XNIO-1 task-1) [org.jboss.ejb.client.invocation] Received MODULE_UNAVAILABLE(9) message for module /playground > DEBUG (XNIO-1 task-1) [org.jboss.ejb.client.invocation] Received CLUSTER_TOPOLOGY_NODE_REMOVAL(18) message for (cluster, node) = (ejb, node1) > DEBUG (XNIO-1 task-1) [org.jboss.ejb.client.invocation] Received CLUSTER_TOPOLOGY_NODE_REMOVAL(18) message for (cluster, node) = (ejb, node1) > ... > {code} > Then node2 is shut down. Again the client get the information, see: > {code} > ... > DEBUG (XNIO-1 task-1) [org.jboss.ejb.client.invocation] Received MODULE_UNAVAILABLE(9) message for module /playground > DEBUG (XNIO-1 task-1) [org.jboss.ejb.client.invocation] Received MODULE_UNAVAILABLE(9) message for module /playground > DEBUG (XNIO-1 task-1) [org.jboss.ejb.client.invocation] Received CLUSTER_TOPOLOGY_NODE_REMOVAL(18) message for (cluster, node) = (ejb, node2) > ... > {code} > Finally node3 is being shut down. Now the client only get the following information: > {code} > ... > DEBUG (XNIO-1 task-1) [org.jboss.ejb.client.invocation] Received MODULE_UNAVAILABLE(9) message for module /playground > DEBUG (XNIO-1 task-1) [org.jboss.ejb.client.invocation] Received MODULE_UNAVAILABLE(9) message for module /playground > ... > {code} > This mean the _node3_ is not being informed about the fact that the last node of the cluster has been stopped. > From this point on the client is always getting {{Caused by: java.net.ConnectException: Connection refused}} > Now node1 is started again, resulting in the following output for {{connectedNodes}} and the {{availableNodes}}: > {code} > ... > INFO (ThreadPoolTaskExecutor-1) [com.jboss.examples.ejb.CustomClusterNodeSelector] connectedNodes(1) '[node1]', availableNodes(2) '[node3, node1]' > ... > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3686) [DMN Designer] Boxed expressions - Decision Table - Enable right click on Decision Table header

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-3686?page=com.atlassian.jira.plugi... ] Jozef Marko commented on DROOLS-3686: ------------------------------------- [~karreiro] I am doing my best but can't promise, so I propose If you have other task than this to land in 7.4 please do them at first then regardless on my progress on DROOLS-3175 start working on this. > [DMN Designer] Boxed expressions - Decision Table - Enable right click on Decision Table header > ----------------------------------------------------------------------------------------------- > > Key: DROOLS-3686 > URL: https://issues.jboss.org/browse/DROOLS-3686 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Affects Versions: 7.18.0.Final > Reporter: Guilherme Carreiro > Assignee: Guilherme Carreiro > Priority: Major > Labels: drools-tools > > Enable right click on Decision Table header. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3674) UX proposal for error reporting after test run

by Michael Anstis (Jira)

[ https://issues.jboss.org/browse/DROOLS-3674?page=com.atlassian.jira.plugi... ] Michael Anstis commented on DROOLS-3674: ---------------------------------------- [~danielezonca] DMN just uses https://www.patternfly.org/pattern-library/widgets/#popover The issue you'll have is using a DOM component (the popover) with the Canvas _cell_ Mouse Over Event. DMN only shows the popover in response to an _edit_ action. So I have a Lienzo Double Click Event handler attached to the Grid that adds a DIV to the DOM at the mouse pointer position, adds the popover HTML to the content and programmatically shows the popover. You'd need to add the DIV to the DOM in the column renderer for invalid cells, add the popover HTML to the DIV and suitable Bootstrap configuration to handle the hover state... but then again you probably knew this much :-) > UX proposal for error reporting after test run > ---------------------------------------------- > > Key: DROOLS-3674 > URL: https://issues.jboss.org/browse/DROOLS-3674 > Project: Drools > Issue Type: Task > Components: Scenario Simulation and Testing > Reporter: Daniele Zonca > Assignee: tao zhu > Priority: Major > Labels: ScenarioSimulation, UXTeam > Attachments: Error reporting after test run-popup.png, Error reporting after test run.png > > > As user after a test run, I want see not only the cell that are not correct (red background) but also the reason. > For instance have the possibility to see the actual value that is different from the expected or the error message. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3674) UX proposal for error reporting after test run

by Daniele Zonca (Jira)

[ https://issues.jboss.org/browse/DROOLS-3674?page=com.atlassian.jira.plugi... ] Daniele Zonca commented on DROOLS-3674: --------------------------------------- [~zhutaojiajia] I think it is fine. Do you suggest different kind of error message for error like "wrong format" and "the actual value is XYZ"? [~manstis] Do you think we can reuse DMN Editor popover component for that? Is it Stunner related or it can be reused? Do you have a link to that? > UX proposal for error reporting after test run > ---------------------------------------------- > > Key: DROOLS-3674 > URL: https://issues.jboss.org/browse/DROOLS-3674 > Project: Drools > Issue Type: Task > Components: Scenario Simulation and Testing > Reporter: Daniele Zonca > Assignee: tao zhu > Priority: Major > Labels: ScenarioSimulation, UXTeam > Attachments: Error reporting after test run-popup.png, Error reporting after test run.png > > > As user after a test run, I want see not only the cell that are not correct (red background) but also the reason. > For instance have the possibility to see the actual value that is different from the expected or the error message. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-599) Build Openshift 3.11 Cluster On B15

by Filip Brychta (Jira)

[ https://issues.jboss.org/browse/SWSQE-599?page=com.atlassian.jira.plugin.... ] Filip Brychta closed SWSQE-599. ------------------------------- Resolution: Duplicate Duplicate of SWSQE-604 > Build Openshift 3.11 Cluster On B15 > ----------------------------------- > > Key: SWSQE-599 > URL: https://issues.jboss.org/browse/SWSQE-599 > Project: Kiali QE > Issue Type: QE Task > Reporter: Matt Mahoney > Assignee: Michael Foley > Priority: Major > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3688) Implement usage of ScenarioHeaderMetaData.getMetadataType

by Gabriele Cardosi (Jira)

Gabriele Cardosi created DROOLS-3688: ---------------------------------------- Summary: Implement usage of ScenarioHeaderMetaData.getMetadataType Key: DROOLS-3688 URL: https://issues.jboss.org/browse/DROOLS-3688 Project: Drools Issue Type: Enhancement Reporter: Gabriele Cardosi Assignee: Anna Baker Inside _ScenarioHeaderMetaData_ there are two flags, _instanceHeader_ and _propertyHeader_, used all over the client code to drive code execution. A new enum has been created, _ScenarioHeaderMetaData.MetadataType_, and a specific property/getter, _ScenarioHeaderMetaData.getMetadataType()_. Replace everywhere (with the exception for single line checks) the usage of _ScenarioHeaderMetaData.isInstanceHeader()_ and _ScenarioHeaderMetaData.isPropertyHeader()_ with _ScenarioHeaderMetaData.getMetadataType()_, and adapt the code to use that enum instead of the boolean. That should remove all the "if" with a more robust and readable "switch" -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-618) Move Bookinfo to Kiali Test Mesh Operator

by Guilherme Baufaker Rêgo (Jira)

Guilherme Baufaker Rêgo created SWSQE-618: --------------------------------------------- Summary: Move Bookinfo to Kiali Test Mesh Operator Key: SWSQE-618 URL: https://issues.jboss.org/browse/SWSQE-618 Project: Kiali QE Issue Type: Sub-task Reporter: Guilherme Baufaker Rêgo Assignee: Michael Foley Moving Bookinfo to Kiali Test Meshin order to get the automatic injection of maistra -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-618) Move Bookinfo to Kiali Test Mesh Operator

by Guilherme Baufaker Rêgo (Jira)

[ https://issues.jboss.org/browse/SWSQE-618?page=com.atlassian.jira.plugin.... ] Guilherme Baufaker Rêgo reassigned SWSQE-618: --------------------------------------------- Assignee: Guilherme Baufaker Rêgo (was: Michael Foley) > Move Bookinfo to Kiali Test Mesh Operator > ----------------------------------------- > > Key: SWSQE-618 > URL: https://issues.jboss.org/browse/SWSQE-618 > Project: Kiali QE > Issue Type: Sub-task > Reporter: Guilherme Baufaker Rêgo > Assignee: Guilherme Baufaker Rêgo > Priority: Major > > Moving Bookinfo to Kiali Test Meshin order to get the automatic injection of maistra -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 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 February 2019