[JBoss JIRA] (DROOLS-5094) KIE-Base and KIE-Session break Test Scenario (Legacy) rhdm 7 (v 7.5.1 on EAP 7.2) Windows 10
by Charles Herrick (Jira)
[ https://issues.redhat.com/browse/DROOLS-5094?page=com.atlassian.jira.plug... ]
Charles Herrick updated DROOLS-5094:
------------------------------------
Attachment: image006.jpg
image007.png
image008.jpg
These are NOT editable/un-choosable in rhdm 7.5.1 Decision Central Test Scenario (Legacy). Once they KIE-Base and KIE-Session are set in the Project > Settings, they are NOT able to be un-set in the Test Scenario (Legacy). And if they are there, the Test Scenario (Legacy) run-scenario will FAIL immediately.
[cid:image006.jpg@01D5ED48.6ED79CB0]
e: Charles.Herrick(a)perficient.com<mailto:Charles.Herrick@perficient.com>
t: Texas Time
--
Charles Herrick, Technical Architect
m: 512-289-0926 | NASDAQ: PRFT | Perficient.com<http://www.perficient.com/>
From: Toni Rikkola (Jira) <issues(a)jboss.org>
Sent: Thursday, February 27, 2020 2:55 AM
To: Charles Herrick <Charles.Herrick(a)perficient.com>
Subject: [JBoss JIRA] (DROOLS-5094) KIE-Base and KIE-Session break Test Scenario (Legacy) rhdm 7 (v 7.5.1 on EAP 7.2) Windows 10
[cid:image002.png@01D5ED48.6EC04420]
Toni Rikkola<https://linkcheck.perficient.com/?url=https%3A%2F%2Fissues.redhat.com%2Fs...> commented on [Bug] DROOLS-5094<https://linkcheck.perficient.com/?url=https%3A%2F%2Fissues.redhat.com%2Fb...>
Re: KIE-Base and KIE-Session break Test Scenario (Legacy) rhdm 7 (v 7.5.1 on EAP 7.2) Windows 10<https://linkcheck.perficient.com/?url=https%3A%2F%2Fissues.redhat.com%2Fb...>
If you open the Test Scenario editor and select the Settings-tab you can find two dropdowns that let you select the kbase and ksession that the Test Scenario uses.
[Add Comment]<https://linkcheck.perficient.com/?url=https%3A%2F%2Fissues.redhat.com%2Fb...>
Add Comment<https://linkcheck.perficient.com/?url=https%3A%2F%2Fissues.redhat.com%2Fb...>
This message was sent by Atlassian Jira (v7.13.8#713008-sha1:1606a5c)
[Image removed by sender. Atlassian logo]
> KIE-Base and KIE-Session break Test Scenario (Legacy) rhdm 7 (v 7.5.1 on EAP 7.2) Windows 10
> --------------------------------------------------------------------------------------------
>
> Key: DROOLS-5094
> URL: https://issues.redhat.com/browse/DROOLS-5094
> Project: Drools
> Issue Type: Bug
> Components: Test Scenarios Editor
> Affects Versions: 7.26.0.Final
> Reporter: Charles Herrick
> Assignee: Toni Rikkola
> Priority: Critical
> Attachments: image006.jpg, image007.png, image008.jpg
>
>
> bug[1]: Once you set the KIE-Base and a KIE-Session in Settings on a Project, subsequent Test Scenario (Legacy) inherit/adopt the KIE-Base and KIE-Session. The run-scenario fails without even running.
> Workaround:
> 1. Create and build the Test Scenario (Legacy)
> 2. Download the Test Scenario (creates an XML file)
> 3. Edit the XML file to set the Session to :
> <ksessions>
> <string>defaultKieSession</string>
> </ksessions>
> 4. Delete the Test Scenario from Decision-Manager > Space > Project > Assets.
> 5. Import Asset > the edited XML file.
> Now the Test Scenario will run.
> Bug[2]: In the Settings for a specific Test Scenario (Legacy) the KIE-Base and KIE-Session are NOT editable and can not be changed. To fix this you have to follow the workaround.
> Versions: Windows 10, rhdm 7 v 7.5.1, EAP v 7.2, Drools: rhdmAdmin (About) == 7.26 Final
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months
[JBoss JIRA] (SWSQE-1077) Kiali Test For Istio.io
by Matthew Mahoney (Jira)
[ https://issues.redhat.com/browse/SWSQE-1077?page=com.atlassian.jira.plugi... ]
Matthew Mahoney updated SWSQE-1077:
-----------------------------------
Description:
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) BrianA 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' to validate the Istio/Kiali integration is properly functioning.
was:
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) BrianA 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.
> 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
> Priority: Major
> Labels: infrastructure
>
> 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) BrianA 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' to validate the Istio/Kiali integration is properly functioning.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months
[JBoss JIRA] (SWSQE-1077) Kiali Test For Istio.io
by Matthew Mahoney (Jira)
[ https://issues.redhat.com/browse/SWSQE-1077?page=com.atlassian.jira.plugi... ]
Matthew Mahoney updated SWSQE-1077:
-----------------------------------
Description:
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) BrianA 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.
was:
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.
> 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
> Priority: Major
> Labels: infrastructure
>
> 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) BrianA 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)
6 years, 2 months
[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)
6 years, 2 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)
6 years, 2 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)
6 years, 2 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)
6 years, 2 months