[JBoss JIRA] (SWSQE-1077) Kiali Test For Istio.io
by Matthew Mahoney (Jira)
Matthew Mahoney created SWSQE-1077:
--------------------------------------
Summary: Kiali Test For Istio.io
Key: SWSQE-1077
URL: https://issues.redhat.com/browse/SWSQE-1077
Project: Kiali QE
Issue Type: QE Task
Reporter: Matthew Mahoney
The Istio.io team is requesting a Kiali test case that can be run on each submitted PR. The purpose of this test case is to validate that Kiali is not broken upon a PR submittal.
Meeting with [~brian.avery] [~gbaufake]:
1) BrinanA to port existing Kiali test case that was developed in old Istio.io test framework to new istiso.io framework
https://github.com/istio/istio/blob/master/tests/e2e/tests/kiali/kiali_te...
2) Kiali team then to add an api test case(s) via 'curl' that to validate the Istio/Kiali integration is properly functioning.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 9 months
[JBoss JIRA] (DROOLS-4963) [DMN Designer] Data Types: Save/cancel icons not visible when there are many constraints and RHS dock open
by Michael Anstis (Jira)
[ https://issues.redhat.com/browse/DROOLS-4963?page=com.atlassian.jira.plug... ]
Michael Anstis updated DROOLS-4963:
-----------------------------------
Summary: [DMN Designer] Data Types: Save/cancel icons not visible when there are many constraints and RHS dock open (was: [DMN Designer] Type designer does not show save/cancel when many constraints are presents and the inspector is open)
> [DMN Designer] Data Types: Save/cancel icons not visible when there are many constraints and RHS dock open
> ----------------------------------------------------------------------------------------------------------
>
> Key: DROOLS-4963
> URL: https://issues.redhat.com/browse/DROOLS-4963
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.32.0.Final
> Reporter: Edoardo Vacchi
> Assignee: Toni Rikkola
> Priority: Major
> Labels: drools-tools
> Attachments: Screenshot from 2020-01-22 16-16-29.png
>
>
> hiding the inspector on the right-hand side uncovers the save/cancel buttons
> !Screenshot from 2020-01-22 16-16-29.png|thumbnail!
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 9 months
[JBoss JIRA] (JGRP-2457) Make time and byte values more legible
by Bela Ban (Jira)
[ https://issues.redhat.com/browse/JGRP-2457?page=com.atlassian.jira.plugin... ]
Bela Ban updated JGRP-2457:
---------------------------
Description:
In an XML configuration, we can already define {{send_buf_size=20M}}, but when printing protocol attribute values, we'll print {{20000000}} instead.
Change this to print time and bytes values in a more readable format, for all protocol attributes.
Examples:
* {{max_credits=3000000}} -> {{max_credits=3m}} // bytes
* {{time=45000}} -> {{time=45s}} // time
* {{avg_delivery_time=250.09us}} (note the suffix) // time
* {{number_of_blockings=234986}} -> {{number_of_blockings=234'986}} // scalar
was:
In an XML configuration, we can already define {{send_buf_size=20M}}, but when printing protocol attribute values, we'll print {{20000000}} instead.
Change this to print time and bytes values in a more readable format, for all protocol attributes.
Examples:
* {{max_credits=3000000}} -> {{max_credits=3m}}
* {{time=45000}} -> {{time=45s}}
* {{avg_delivery_time=250.09us}} (note the suffix)
> Make time and byte values more legible
> --------------------------------------
>
> Key: JGRP-2457
> URL: https://issues.redhat.com/browse/JGRP-2457
> Project: JGroups
> Issue Type: Enhancement
> Reporter: Bela Ban
> Assignee: Bela Ban
> Priority: Minor
> Fix For: 5.0
>
>
> In an XML configuration, we can already define {{send_buf_size=20M}}, but when printing protocol attribute values, we'll print {{20000000}} instead.
> Change this to print time and bytes values in a more readable format, for all protocol attributes.
> Examples:
> * {{max_credits=3000000}} -> {{max_credits=3m}} // bytes
> * {{time=45000}} -> {{time=45s}} // time
> * {{avg_delivery_time=250.09us}} (note the suffix) // time
> * {{number_of_blockings=234986}} -> {{number_of_blockings=234'986}} // scalar
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 9 months
[JBoss JIRA] (WFCORE-4860) Performance degradation with the LogContextSelector on Java 11
by James Perkins (Jira)
[ https://issues.redhat.com/browse/WFCORE-4860?page=com.atlassian.jira.plug... ]
James Perkins updated WFCORE-4860:
----------------------------------
Issue Type: Enhancement (was: Bug)
> Performance degradation with the LogContextSelector on Java 11
> ---------------------------------------------------------------
>
> Key: WFCORE-4860
> URL: https://issues.redhat.com/browse/WFCORE-4860
> Project: WildFly Core
> Issue Type: Enhancement
> Components: Logging
> Reporter: James Perkins
> Assignee: James Perkins
> Priority: Major
>
> As described in LOGMGR-263 there is a performance impact on Java 11 when using the {{ClassLoaderLogContextSelector}}. In WildFly for users that do not use per-deployment logging we could get around this by not using that log context selector. This would not fix the performance impact for users using Java 11 and per-deployment logging however.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 9 months
[JBoss JIRA] (WFLY-13168) Invalidation caches use wrong key affinity
by Paul Ferraro (Jira)
Paul Ferraro created WFLY-13168:
-----------------------------------
Summary: Invalidation caches use wrong key affinity
Key: WFLY-13168
URL: https://issues.redhat.com/browse/WFLY-13168
Project: WildFly
Issue Type: Bug
Components: Clustering
Affects Versions: 19.0.0.Beta2, 18.0.1.Final
Reporter: Paul Ferraro
Assignee: Paul Ferraro
Now that invalidation caches perform entry locking via the primary owner, requests should retain affinity with the primary owner. Otherwise, normal operations are prone to lock timeouts.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 9 months