[JBoss JIRA] (DROOLS-2532) UX design for scenario simulation
by Liz Clayton (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2532?page=com.atlassian.jira.plugi... ]
Liz Clayton updated DROOLS-2532:
--------------------------------
Attachment: (was: Alternative.pdf)
> UX design for scenario simulation
> ---------------------------------
>
> Key: DROOLS-2532
> URL: https://issues.jboss.org/browse/DROOLS-2532
> Project: Drools
> Issue Type: Task
> Reporter: Liz Clayton
> Assignee: Liz Clayton
> Labels: Appformer, UX, UXTeam
>
> As Aimee or Cameron I want to:
> * Easily create a test scenario template through the use of variable/data object placeholders so that I can create test scenarios against a single decision.
> * Define test scenarios through a UI so I can develop basic task scenarios with minimal engagement from IT.
> * Run a test scenario simulation so that I can verify the expected results against test simulation results.
> Verification conditions:
> Provide wireframe design and click-thru prototype which includes the following views:
> * Overview (properties)
> * Scenario Template
> * Scenarios Input Screen
> * Results
> * Code View
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month
[JBoss JIRA] (WFCORE-2886) remove-handler operation succeeds when removing non-existent handler
by James Perkins (JIRA)
[ https://issues.jboss.org/browse/WFCORE-2886?page=com.atlassian.jira.plugi... ]
James Perkins closed WFCORE-2886.
---------------------------------
Resolution: Won't Fix
I'm closing this as won't fix since it's likely not a huge issue to remove a handler that's not assigned to either the async-handler or a logger. If you feel this is usability issue please reopen and we can get a fix together.
> remove-handler operation succeeds when removing non-existent handler
> --------------------------------------------------------------------
>
> Key: WFCORE-2886
> URL: https://issues.jboss.org/browse/WFCORE-2886
> Project: WildFly Core
> Issue Type: Bug
> Components: Logging
> Reporter: Michal Petrov
> Assignee: Michal Petrov
>
> When trying to remove a handler that doesn't exist the operation should fail. E.g.
> {code}
> /subsystem=logging/root-logger=ROOT:remove-handler(name="ABC")
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month
[JBoss JIRA] (SWSQE-287) Istiooc command, ansible installer and installation template Suport Kiali Install
by Matt Mahoney (JIRA)
Matt Mahoney created SWSQE-287:
----------------------------------
Summary: Istiooc command, ansible installer and installation template Suport Kiali Install
Key: SWSQE-287
URL: https://issues.jboss.org/browse/SWSQE-287
Project: Kiali QE
Issue Type: Story
Reporter: Matt Mahoney
Assignee: Michael Foley
The istiooc command, ansible installer and installation template have been updated to support installation of kiali, please pull down the latest versions and try out the integration.
The istiooc command can be obtained from the release page
https://github.com/openshift-istio/origin/releases/tag/istio-3.9-0.8.0-al...
and adds the following options
--istio-kiali-password - Specify the password for accessing the Kiali console
--istio-kiali-username - Specify the username for accessing the Kiali console
--istio-kiali-version - Specify the tag for Istio Kiali images (defaults to '0.3.1.Alpha')
Both username and password need to be supplied for kiali to be installed.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month
[JBoss JIRA] (DROOLS-2532) UX design for scenario simulation
by Liz Clayton (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2532?page=com.atlassian.jira.plugi... ]
Liz Clayton commented on DROOLS-2532:
-------------------------------------
[~danielezonca] [~jomarko] I've been getting feedback that people are leaning toward the pop-over input option. So I've iterated on that to resolve some of the things about that that bug me. I have a demo of just the "template" pop-over interaction:
https://cdn.rawgit.com/lclay2/bxms-uxd-sandbox/dc0217fe/design/demo/index...
Here's what's in this demo:
* Added the input box inline in the table cell (but hid the borders.)
* Created a button for the table cell to spawn a pop-over only for adding a data object. User can use this to populate the expression input field or type directly into it.
* Added + icon button to the column headers to allow users to add columns dynamically. Could also do the table using contextual menu and/or table actions in a toolbar. Only the Expect column works in the demo.
* Because I am adding more affordances to add columns inline, I removed the multi-select on the Data Object tree - which should simplify the whole experience a bit.
Thanks for reviewing all of the iterations, please let me know what you think of this. I'm actually leaning toward this one.
> UX design for scenario simulation
> ---------------------------------
>
> Key: DROOLS-2532
> URL: https://issues.jboss.org/browse/DROOLS-2532
> Project: Drools
> Issue Type: Task
> Reporter: Liz Clayton
> Assignee: Liz Clayton
> Labels: Appformer, UX, UXTeam
> Attachments: Alternative.pdf, RoundF2.pdf
>
>
> As Aimee or Cameron I want to:
> * Easily create a test scenario template through the use of variable/data object placeholders so that I can create test scenarios against a single decision.
> * Define test scenarios through a UI so I can develop basic task scenarios with minimal engagement from IT.
> * Run a test scenario simulation so that I can verify the expected results against test simulation results.
> Verification conditions:
> Provide wireframe design and click-thru prototype which includes the following views:
> * Overview (properties)
> * Scenario Template
> * Scenarios Input Screen
> * Results
> * Code View
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month
[JBoss JIRA] (ELY-618) Dead code in DEREncoder
by Farah Juma (JIRA)
[ https://issues.jboss.org/browse/ELY-618?page=com.atlassian.jira.plugin.sy... ]
Farah Juma commented on ELY-618:
--------------------------------
[~ivassile] Thanks for catching this, it's a bug. As you pointed out, the ASN1 tags that are currently being used are single octet but we'll want to allow high tag numbers for things like {{startExplicit}} and {{encodeImplicit}}. I think we'll want to try to tweak {{DEREncoder}} to be able to handle the high-tag-number form.
> Dead code in DEREncoder
> -----------------------
>
> Key: ELY-618
> URL: https://issues.jboss.org/browse/ELY-618
> Project: WildFly Elytron
> Issue Type: Bug
> Affects Versions: 1.1.0.Beta7
> Reporter: Ondrej Lukas
> Assignee: Ilia Vassilev
> Labels: static_analysis
>
> There is an unintentional dead code in writeTag method of org.wildfly.security.asn1.DEREncoder. Variable {{tagNumber}} can be assigned to 31 as its maximal value from {{int tagNumber = tag & TAG_NUMBER_MASK;}} (because {{TAG_NUMBER_MASK = 0x1f}}) on line 576 [1] which means that condition {{if (tagNumber < 128)}} on line 582 is always true. It causes that else branch is never executed.
> [1] https://github.com/wildfly-security/wildfly-elytron/blob/4453ea40a7a617b6...
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month
[JBoss JIRA] (WFCORE-3920) Update the testsuite to make use of the utilities for certificate generation instead of using pre-generated CAs and certs
by Justin Cook (JIRA)
Justin Cook created WFCORE-3920:
-----------------------------------
Summary: Update the testsuite to make use of the utilities for certificate generation instead of using pre-generated CAs and certs
Key: WFCORE-3920
URL: https://issues.jboss.org/browse/WFCORE-3920
Project: WildFly Core
Issue Type: Task
Components: Test Suite
Reporter: Justin Cook
Assignee: Justin Cook
Our testsuite currently makes use of pre-generated CAs and certs. This results in issues when the certificates expire since the testsuite then needs to be updated with newly generated CAs and certs. This task is to update our testsuite to dynamically generate the needed certificates using Elytron's certificate generation utilities (e.g., org.wildfly.security.x500.cert.X509CertificateBuilder, org.wildfly.security.x500.cert.SelfSignedX509CertificateAndSigningKey.builder(), etc.).
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month