[JBoss JIRA] (DROOLS-3053) Warning dialog of column type change in Scenario grid
by Sarah Rambacher (Jira)
[ https://issues.jboss.org/browse/DROOLS-3053?page=com.atlassian.jira.plugi... ]
Sarah Rambacher commented on DROOLS-3053:
-----------------------------------------
PR here: https://github.com/srambach/BxMS-frontend/pull/77
Rawgit here: https://rawgit.com/srambach/BxMS-frontend/3edb0d55ae3ee3402e353546b2cd2a4...
[~uxdlc][~danielezonca][~gabriolo][~stetson.robinson]
> Warning dialog of column type change in Scenario grid
> -----------------------------------------------------
>
> Key: DROOLS-3053
> URL: https://issues.jboss.org/browse/DROOLS-3053
> Project: Drools
> Issue Type: Task
> Components: Scenario Simulation and Testing
> Reporter: Daniele Zonca
> Assignee: Gabriele Cardosi
> Priority: Minor
> Labels: UX, UXTeam
> Attachments: Final-WarningA.png, Final-WarningB.png, Screenshot from 2018-10-04 17-44-51.png, Screenshot from 2018-10-04 17-45-21.png
>
>
> Implement a warning popup when the user changes the type of a column that has been already populated.
> To be done/merged *after* DROOLS-3051.
> *Acceptance criteria*
> - If the column contains no value, no confirmation is needed
> - If old and new types are the same the user has to decide if the values should be removed or not
> - If old and new types are not the same the user has to accept that old values will be removed
> - All warning popups should contains also a "Cancel" command to abort the edit
> - If the user try to update the column type with the same column type no warning should be raised and data should stay untouched
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (ELY-1695) X509EvidenceVerificationSuiteChild AssertionError when run in multiple profiles
by Justin Cook (Jira)
[ https://issues.jboss.org/browse/ELY-1695?page=com.atlassian.jira.plugin.s... ]
Justin Cook updated ELY-1695:
-----------------------------
Priority: Major (was: Blocker)
> X509EvidenceVerificationSuiteChild AssertionError when run in multiple profiles
> -------------------------------------------------------------------------------
>
> Key: ELY-1695
> URL: https://issues.jboss.org/browse/ELY-1695
> Project: WildFly Elytron
> Issue Type: Bug
> Components: Testsuite
> Reporter: Justin Cook
> Assignee: Justin Cook
> Priority: Major
>
> When running the testsuite with multiple profiles (default-test,java8-test,java9-test), the following error happens for the second and third (java8-test and java8-test) profiles:
> {code}
> Running org.wildfly.security.ldap.LdapTestSuite
> Tests run: 63, Failures: 2, Errors: 0, Skipped: 0, Time elapsed: 19.83 sec <<< FAILURE! - in org.wildfly.security.ldap.LdapTestSuite
> testX509Auth(org.wildfly.security.ldap.X509EvidenceVerificationSuiteChild) Time elapsed: 0.121 sec <<< FAILURE!
> java.lang.AssertionError
> at org.wildfly.security.ldap.X509EvidenceVerificationSuiteChild.testX509AuthInternal(X509EvidenceVerificationSuiteChild.java:80)
> at org.wildfly.security.ldap.X509EvidenceVerificationSuiteChild.testX509Auth(X509EvidenceVerificationSuiteChild.java:49)
> at org.wildfly.security.ldap.DirContextFactoryRule$1.evaluate(DirContextFactoryRule.java:218)
> testX509AuthBinary(org.wildfly.security.ldap.X509EvidenceVerificationSuiteChild) Time elapsed: 0.116 sec <<< FAILURE!
> java.lang.AssertionError
> at org.wildfly.security.ldap.X509EvidenceVerificationSuiteChild.testX509AuthInternal(X509EvidenceVerificationSuiteChild.java:80)
> at org.wildfly.security.ldap.X509EvidenceVerificationSuiteChild.testX509AuthBinary(X509EvidenceVerificationSuiteChild.java:54)
> at org.wildfly.security.ldap.DirContextFactoryRule$1.evaluate(DirContextFactoryRule.java:218)
> Results :
> Failed tests:
> X509EvidenceVerificationSuiteChild.testX509Auth:49->testX509AuthInternal:80
> X509EvidenceVerificationSuiteChild.testX509AuthBinary:54->testX509AuthInternal:80
> {code}
> Setting to blocker since it prevents running the Java8 tests
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (ELY-1695) X509EvidenceVerificationSuiteChild AssertionError when run in multiple profiles
by Justin Cook (Jira)
[ https://issues.jboss.org/browse/ELY-1695?page=com.atlassian.jira.plugin.s... ]
Justin Cook updated ELY-1695:
-----------------------------
Description:
When running the testsuite with multiple profiles (default-test,java8-test,java9-test), the following error happens for the second and third (java8-test and java8-test) profiles:
{code}
Running org.wildfly.security.ldap.LdapTestSuite
Tests run: 63, Failures: 2, Errors: 0, Skipped: 0, Time elapsed: 19.83 sec <<< FAILURE! - in org.wildfly.security.ldap.LdapTestSuite
testX509Auth(org.wildfly.security.ldap.X509EvidenceVerificationSuiteChild) Time elapsed: 0.121 sec <<< FAILURE!
java.lang.AssertionError
at org.wildfly.security.ldap.X509EvidenceVerificationSuiteChild.testX509AuthInternal(X509EvidenceVerificationSuiteChild.java:80)
at org.wildfly.security.ldap.X509EvidenceVerificationSuiteChild.testX509Auth(X509EvidenceVerificationSuiteChild.java:49)
at org.wildfly.security.ldap.DirContextFactoryRule$1.evaluate(DirContextFactoryRule.java:218)
testX509AuthBinary(org.wildfly.security.ldap.X509EvidenceVerificationSuiteChild) Time elapsed: 0.116 sec <<< FAILURE!
java.lang.AssertionError
at org.wildfly.security.ldap.X509EvidenceVerificationSuiteChild.testX509AuthInternal(X509EvidenceVerificationSuiteChild.java:80)
at org.wildfly.security.ldap.X509EvidenceVerificationSuiteChild.testX509AuthBinary(X509EvidenceVerificationSuiteChild.java:54)
at org.wildfly.security.ldap.DirContextFactoryRule$1.evaluate(DirContextFactoryRule.java:218)
Results :
Failed tests:
X509EvidenceVerificationSuiteChild.testX509Auth:49->testX509AuthInternal:80
X509EvidenceVerificationSuiteChild.testX509AuthBinary:54->testX509AuthInternal:80
{code}
was:
When running the testsuite with multiple profiles (default-test,java8-test,java9-test), the following error happens for the second and third (java8-test and java8-test) profiles:
{code}
Running org.wildfly.security.ldap.LdapTestSuite
Tests run: 63, Failures: 2, Errors: 0, Skipped: 0, Time elapsed: 19.83 sec <<< FAILURE! - in org.wildfly.security.ldap.LdapTestSuite
testX509Auth(org.wildfly.security.ldap.X509EvidenceVerificationSuiteChild) Time elapsed: 0.121 sec <<< FAILURE!
java.lang.AssertionError
at org.wildfly.security.ldap.X509EvidenceVerificationSuiteChild.testX509AuthInternal(X509EvidenceVerificationSuiteChild.java:80)
at org.wildfly.security.ldap.X509EvidenceVerificationSuiteChild.testX509Auth(X509EvidenceVerificationSuiteChild.java:49)
at org.wildfly.security.ldap.DirContextFactoryRule$1.evaluate(DirContextFactoryRule.java:218)
testX509AuthBinary(org.wildfly.security.ldap.X509EvidenceVerificationSuiteChild) Time elapsed: 0.116 sec <<< FAILURE!
java.lang.AssertionError
at org.wildfly.security.ldap.X509EvidenceVerificationSuiteChild.testX509AuthInternal(X509EvidenceVerificationSuiteChild.java:80)
at org.wildfly.security.ldap.X509EvidenceVerificationSuiteChild.testX509AuthBinary(X509EvidenceVerificationSuiteChild.java:54)
at org.wildfly.security.ldap.DirContextFactoryRule$1.evaluate(DirContextFactoryRule.java:218)
Results :
Failed tests:
X509EvidenceVerificationSuiteChild.testX509Auth:49->testX509AuthInternal:80
X509EvidenceVerificationSuiteChild.testX509AuthBinary:54->testX509AuthInternal:80
{code}
Setting to blocker since it prevents running the Java8 tests
> X509EvidenceVerificationSuiteChild AssertionError when run in multiple profiles
> -------------------------------------------------------------------------------
>
> Key: ELY-1695
> URL: https://issues.jboss.org/browse/ELY-1695
> Project: WildFly Elytron
> Issue Type: Bug
> Components: Testsuite
> Reporter: Justin Cook
> Assignee: Justin Cook
> Priority: Major
>
> When running the testsuite with multiple profiles (default-test,java8-test,java9-test), the following error happens for the second and third (java8-test and java8-test) profiles:
> {code}
> Running org.wildfly.security.ldap.LdapTestSuite
> Tests run: 63, Failures: 2, Errors: 0, Skipped: 0, Time elapsed: 19.83 sec <<< FAILURE! - in org.wildfly.security.ldap.LdapTestSuite
> testX509Auth(org.wildfly.security.ldap.X509EvidenceVerificationSuiteChild) Time elapsed: 0.121 sec <<< FAILURE!
> java.lang.AssertionError
> at org.wildfly.security.ldap.X509EvidenceVerificationSuiteChild.testX509AuthInternal(X509EvidenceVerificationSuiteChild.java:80)
> at org.wildfly.security.ldap.X509EvidenceVerificationSuiteChild.testX509Auth(X509EvidenceVerificationSuiteChild.java:49)
> at org.wildfly.security.ldap.DirContextFactoryRule$1.evaluate(DirContextFactoryRule.java:218)
> testX509AuthBinary(org.wildfly.security.ldap.X509EvidenceVerificationSuiteChild) Time elapsed: 0.116 sec <<< FAILURE!
> java.lang.AssertionError
> at org.wildfly.security.ldap.X509EvidenceVerificationSuiteChild.testX509AuthInternal(X509EvidenceVerificationSuiteChild.java:80)
> at org.wildfly.security.ldap.X509EvidenceVerificationSuiteChild.testX509AuthBinary(X509EvidenceVerificationSuiteChild.java:54)
> at org.wildfly.security.ldap.DirContextFactoryRule$1.evaluate(DirContextFactoryRule.java:218)
> Results :
> Failed tests:
> X509EvidenceVerificationSuiteChild.testX509Auth:49->testX509AuthInternal:80
> X509EvidenceVerificationSuiteChild.testX509AuthBinary:54->testX509AuthInternal:80
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (ELY-1695) X509EvidenceVerificationSuiteChild AssertionError when run in multiple profiles
by Justin Cook (Jira)
Justin Cook created ELY-1695:
--------------------------------
Summary: X509EvidenceVerificationSuiteChild AssertionError when run in multiple profiles
Key: ELY-1695
URL: https://issues.jboss.org/browse/ELY-1695
Project: WildFly Elytron
Issue Type: Bug
Components: Testsuite
Reporter: Justin Cook
Assignee: Justin Cook
When running the testsuite with multiple profiles (default-test,java8-test,java9-test), the following error happens for the second and third (java8-test and java8-test) profiles:
{code}
Running org.wildfly.security.ldap.LdapTestSuite
Tests run: 63, Failures: 2, Errors: 0, Skipped: 0, Time elapsed: 19.83 sec <<< FAILURE! - in org.wildfly.security.ldap.LdapTestSuite
testX509Auth(org.wildfly.security.ldap.X509EvidenceVerificationSuiteChild) Time elapsed: 0.121 sec <<< FAILURE!
java.lang.AssertionError
at org.wildfly.security.ldap.X509EvidenceVerificationSuiteChild.testX509AuthInternal(X509EvidenceVerificationSuiteChild.java:80)
at org.wildfly.security.ldap.X509EvidenceVerificationSuiteChild.testX509Auth(X509EvidenceVerificationSuiteChild.java:49)
at org.wildfly.security.ldap.DirContextFactoryRule$1.evaluate(DirContextFactoryRule.java:218)
testX509AuthBinary(org.wildfly.security.ldap.X509EvidenceVerificationSuiteChild) Time elapsed: 0.116 sec <<< FAILURE!
java.lang.AssertionError
at org.wildfly.security.ldap.X509EvidenceVerificationSuiteChild.testX509AuthInternal(X509EvidenceVerificationSuiteChild.java:80)
at org.wildfly.security.ldap.X509EvidenceVerificationSuiteChild.testX509AuthBinary(X509EvidenceVerificationSuiteChild.java:54)
at org.wildfly.security.ldap.DirContextFactoryRule$1.evaluate(DirContextFactoryRule.java:218)
Results :
Failed tests:
X509EvidenceVerificationSuiteChild.testX509Auth:49->testX509AuthInternal:80
X509EvidenceVerificationSuiteChild.testX509AuthBinary:54->testX509AuthInternal:80
{code}
Setting to blocker since it prevents running the Java8 tests
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (DROOLS-3077) Enhance data type restrictions UX - Decision Table/properties
by Liz Clayton (Jira)
[ https://issues.jboss.org/browse/DROOLS-3077?page=com.atlassian.jira.plugi... ]
Liz Clayton updated DROOLS-3077:
--------------------------------
Sprint: 2018 Week 33-35 (was: 2018 Week 33-35, 2018 Week 42-44)
> Enhance data type restrictions UX - Decision Table/properties
> -------------------------------------------------------------
>
> Key: DROOLS-3077
> URL: https://issues.jboss.org/browse/DROOLS-3077
> Project: Drools
> Issue Type: Story
> Components: DMN Editor
> Reporter: Liz Clayton
> Assignee: Liz Clayton
> Priority: Major
> Labels: UX, UXTeam, drools-tools
> Attachments: DataType selection ('Properties Panel' and 'in-grid').png, Screen Shot 2018-08-10 at 10.23.36 AM.png, Screen Shot 2018-08-24 at 8.38.37 AM.png, Screen Shot 2018-09-28 at 2.44.59 PM.png, date-time.png, date.png, enumration-widget.png, pop-overc.png, pop-overcSpecs.png, read-mode.png, select.png, time.png
>
>
> *Background*
> Persona: Business analyst or Rules practitioner
> Use Cases:
> * From the DMN canvas view - as a user I want to define data type restrictions (one-off instances) from a decision table .
> * From the Data Types dialog - as a user I want the ability to define constraints for the following types: https://docs.google.com/spreadsheets/d/1HLYwi5JrCEU6IxWRge7RCKANLiHCL0d2E...
> Functional considerations/ pre conditions:
> * Consider interaction in light of Property panel and consistency.
> * Underscore the notion of one-off constraints.
> Verification conditions:
> * Scrum team and PO review.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (DROOLS-3000) Enhance data type restrictions UX in DT dialog
by Liz Clayton (Jira)
[ https://issues.jboss.org/browse/DROOLS-3000?page=com.atlassian.jira.plugi... ]
Liz Clayton updated DROOLS-3000:
--------------------------------
Sprint: 2018 Week 33-35 (was: 2018 Week 33-35, 2018 Week 39-41)
> Enhance data type restrictions UX in DT dialog
> ----------------------------------------------
>
> Key: DROOLS-3000
> URL: https://issues.jboss.org/browse/DROOLS-3000
> Project: Drools
> Issue Type: Story
> Components: DMN Editor
> Reporter: Liz Clayton
> Assignee: Liz Clayton
> Priority: Major
> Labels: UX, UXTeam, drools-tools
> Attachments: DataType selection ('Properties Panel' and 'in-grid').png, Screen Shot 2018-08-10 at 10.23.36 AM.png, Screen Shot 2018-08-24 at 8.38.37 AM.png, Screen Shot 2018-09-28 at 2.44.59 PM.png, date-time.png, date.png, enumration-widget.png, pop-overc.png, pop-overcSpecs.png, read-mode.png, select.png, time.png
>
>
> *Background*
> Persona: Business analyst or Rules practitioner
> Use Cases:
> * From the DMN canvas view - as a user I want to define data type restrictions (one-off instances) from a decision table .
> * From the Data Types dialog - as a user I want the ability to define constraints for the following types: https://docs.google.com/spreadsheets/d/1HLYwi5JrCEU6IxWRge7RCKANLiHCL0d2E...
> Functional considerations/ pre conditions:
> * Consider interaction in light of Property panel and consistency.
> * Underscore the notion of one-off constraints.
> Verification conditions:
> * Scrum team and PO review.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (LOGMGR-205) Add ability to watch a logging configuration file for changes and reconfigure the log manager based on the new configuation
by James Perkins (Jira)
[ https://issues.jboss.org/browse/LOGMGR-205?page=com.atlassian.jira.plugin... ]
James Perkins commented on LOGMGR-205:
--------------------------------------
We could just use the {{logging.properties}} to configure logging for the cloud. However we'd lose some things like per-deployment logging and logging profiles.
The ConfigMap sounds interesting though. I don't know much about that, but OT for this it would be interesting if possible to have a ConfigMap to CLI type of thing. However that doesn't really make the configuration immutable.
More of a WildFly thing, but one thing I've thought of too is not using the XML config file for the logging configuration. Essentially the model would be based on a {{logging.properties}} rather than the XML. There are some issues with system properties, paths, etc. that make this not quite work right however. The ability to listen to a file for changes would allow either a management interface or editing the raw file to work though. Though like I said working around the paths ({{relative-to}}) and system properties is a problem.
> Add ability to watch a logging configuration file for changes and reconfigure the log manager based on the new configuation
> ---------------------------------------------------------------------------------------------------------------------------
>
> Key: LOGMGR-205
> URL: https://issues.jboss.org/browse/LOGMGR-205
> Project: JBoss Log Manager
> Issue Type: Feature Request
> Reporter: James Perkins
> Assignee: James Perkins
> Priority: Major
>
> It could be useful to add a utility to watch a {{logging.properties}} file for changes and reconfigure the log manager based on these changes.
> As a test I've created an [example|https://gist.github.com/jamezp/68cd45982ba2b75aa2e95465695ec061] which could use some better options for removing no longer used configured objects.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months