[JBoss JIRA] (WFCORE-4262) product-info command throws java.lang.IllegalArgumentException if patching subsystem is not available
by Bartosz Spyrko-Śmietanko (Jira)
[ https://issues.jboss.org/browse/WFCORE-4262?page=com.atlassian.jira.plugi... ]
Bartosz Spyrko-Śmietanko updated WFCORE-4262:
---------------------------------------------
Labels: downstream_dependency (was: )
> product-info command throws java.lang.IllegalArgumentException if patching subsystem is not available
> -----------------------------------------------------------------------------------------------------
>
> Key: WFCORE-4262
> URL: https://issues.jboss.org/browse/WFCORE-4262
> Project: WildFly Core
> Issue Type: Bug
> Components: CLI
> Environment: JBoss EAP 7.1 CP05 installed via rpm
> Reporter: Bartosz Spyrko-Śmietanko
> Assignee: Bartosz Spyrko-Śmietanko
> Priority: Major
> Labels: downstream_dependency
>
> Executing the product-info command with embed-server is throwing the following exception. It is not possible to reproduce the issue with JBoss installed via zip distribution.
> {code:java}
> [standalone@embedded /] :product-info
> 13:14:42,580 ERROR [org.jboss.as.controller.management-operation] (AeshProcess: 2) WFLYCTL0013: Operation ("report") failed - address: ([]): java.lang.IllegalArgumentException
> at org.jboss.dmr.ModelValue.asList(ModelValue.java:143) [jboss-dmr.jar:1.4.1.Final-redhat-1]
> at org.jboss.dmr.ModelNode.asList(ModelNode.java:1566) [jboss-dmr.jar:1.4.1.Final-redhat-1]
> at org.jboss.as.server.operations.AbstractInstallationReporter$InstallationConfiguration.getLastUpdateDate(AbstractInstallationReporter.java:328)
> at org.jboss.as.server.operations.AbstractInstallationReporter.createProductNode(AbstractInstallationReporter.java:184)
> at org.jboss.as.server.operations.InstallationReportHandler$1.execute(InstallationReportHandler.java:81)
> at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:982)
> at org.jboss.as.controller.AbstractOperationContext.processStages(AbstractOperationContext.java:726)
> at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:450)
> at org.jboss.as.controller.OperationContextImpl.executeOperation(OperationContextImpl.java:1402)
> at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:418)
> at org.jboss.as.controller.ModelControllerImpl.lambda$execute$1(ModelControllerImpl.java:243)
> at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:263) [wildfly-elytron.jar:1.1.11.Final-redhat-00001]
> at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:229) [wildfly-elytron.jar:1.1.11.Final-redhat-00001]
> at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:243)
> at org.jboss.as.controller.ModelControllerClientFactoryImpl$LocalClient.executeOperation(ModelControllerClientFactoryImpl.java:131)
> at org.jboss.as.controller.ModelControllerClientFactoryImpl.lambda$executeInVm$0(ModelControllerClientFactoryImpl.java:296)
> at org.jboss.as.controller.access.InVmAccess.runInVm(InVmAccess.java:85)
> at org.jboss.as.controller.ModelControllerClientFactoryImpl.executeInVm(ModelControllerClientFactoryImpl.java:296)
> at org.jboss.as.controller.ModelControllerClientFactoryImpl.access$000(ModelControllerClientFactoryImpl.java:54)
> at org.jboss.as.controller.ModelControllerClientFactoryImpl$1.executeOperation(ModelControllerClientFactoryImpl.java:77)
> at org.jboss.as.controller.LocalModelControllerClient.execute(LocalModelControllerClient.java:54)
> at org.jboss.as.controller.LocalModelControllerClient.execute(LocalModelControllerClient.java:44)
> at org.jboss.as.controller.client.helpers.DelegatingModelControllerClient.execute(DelegatingModelControllerClient.java:68) [wildfly-controller-client-3.0.19.Final-redhat-00001.jar:3.0.19.Final-redhat-00001]
> at org.jboss.as.cli.embedded.ThreadContextsModelControllerClient.execute(ThreadContextsModelControllerClient.java:69) [wildfly-cli-3.0.19.Final-redhat-00001.jar:3.0.19.Final-redhat-00001]
> at org.jboss.as.cli.impl.CommandExecutor.execute(CommandExecutor.java:654) [wildfly-cli-3.0.19.Final-redhat-00001.jar:3.0.19.Final-redhat-00001]
> at org.jboss.as.cli.impl.CommandContextImpl.lambda$execute$1(CommandContextImpl.java:872) [wildfly-cli-3.0.19.Final-redhat-00001.jar:3.0.19.Final-redhat-00001]
> at org.jboss.as.cli.impl.CommandContextImpl.execute(CommandContextImpl.java:892) [wildfly-cli-3.0.19.Final-redhat-00001.jar:3.0.19.Final-redhat-00001]
> at org.jboss.as.cli.impl.CommandContextImpl.execute(CommandContextImpl.java:871) [wildfly-cli-3.0.19.Final-redhat-00001.jar:3.0.19.Final-redhat-00001]
> at org.jboss.as.cli.handlers.OperationRequestHandler.handle(OperationRequestHandler.java:90) [wildfly-cli-3.0.19.Final-redhat-00001.jar:3.0.19.Final-redhat-00001]
> at org.jboss.as.cli.impl.CommandContextImpl.handle(CommandContextImpl.java:816) [wildfly-cli-3.0.19.Final-redhat-00001.jar:3.0.19.Final-redhat-00001]
> at org.jboss.as.cli.impl.CommandContextImpl.handleSafe(CommandContextImpl.java:917) [wildfly-cli-3.0.19.Final-redhat-00001.jar:3.0.19.Final-redhat-00001]
> at org.jboss.as.cli.impl.CommandContextImpl$2.execute(CommandContextImpl.java:454) [wildfly-cli-3.0.19.Final-redhat-00001.jar:3.0.19.Final-redhat-00001]
> at org.jboss.aesh.console.AeshProcess.run(AeshProcess.java:53) [aesh.jar:0.66.19.redhat-1]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [rt.jar:1.8.0_191]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [rt.jar:1.8.0_191]
> at java.lang.Thread.run(Thread.java:748) [rt.jar:1.8.0_191]
> {
> "outcome" => "failed",
> "rolled-back" => true
> }
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 2 months
[JBoss JIRA] (DROOLS-3430) [DMN Designer] [Edge] Update Name via Name And DataType dialog
by Daniel José dos Santos (Jira)
[ https://issues.jboss.org/browse/DROOLS-3430?page=com.atlassian.jira.plugi... ]
Daniel José dos Santos commented on DROOLS-3430:
------------------------------------------------
This is my Christmas gift! :D
> [DMN Designer] [Edge] Update Name via Name And DataType dialog
> --------------------------------------------------------------
>
> Key: DROOLS-3430
> URL: https://issues.jboss.org/browse/DROOLS-3430
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.16.0.Final
> Environment: Win10, Edge, eap-7.2
> Reporter: Jozef Marko
> Assignee: Daniel José dos Santos
> Priority: Major
> Labels: drools-tools, edge
> Attachments: Screenshot from 2018-12-13 07-50-37.png
>
>
> User can rename boxed expression elements by single click into given grid cell. Then the *Name and DataType dialog* is shown to the user where he can rename the given element. The problem on *Edge* is confirming this renaming. On other browsers renaming is confirmed with clicking somewhere into canvas. On the *Edge* clicking to canvas close the dialog and renaming is discarded.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 2 months
[JBoss JIRA] (DROOLS-3039) [DMN Designer] Item definition change doesn't make designer dirty
by Guilherme Carreiro (Jira)
[ https://issues.jboss.org/browse/DROOLS-3039?page=com.atlassian.jira.plugi... ]
Guilherme Carreiro commented on DROOLS-3039:
--------------------------------------------
[~jomarko],
Thank you for reporting, however the issue no longer reproducible:
!DROOLS-3039.gif!
> [DMN Designer] Item definition change doesn't make designer dirty
> -----------------------------------------------------------------
>
> Key: DROOLS-3039
> URL: https://issues.jboss.org/browse/DROOLS-3039
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.12.0.Final
> Reporter: Jozef Marko
> Assignee: Guilherme Carreiro
> Priority: Minor
> Labels: drools-tools
> Attachments: DROOLS-3039.gif
>
>
> Changes in item definition definitions don't make the designer dirty. User can then can easily overlook he should save changes before closing the designer.
> h2. Acceptance test
> Check editor is dirty:
> - Definitions moved
> - Definitions declared
> - Definitions removed
> - Definitions edited
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 2 months
[JBoss JIRA] (DROOLS-3039) [DMN Designer] Item definition change doesn't make designer dirty
by Guilherme Carreiro (Jira)
[ https://issues.jboss.org/browse/DROOLS-3039?page=com.atlassian.jira.plugi... ]
Guilherme Carreiro edited comment on DROOLS-3039 at 12/21/18 10:59 AM:
-----------------------------------------------------------------------
[~jomarko],
Thank you for reporting, however the issue no longer reproducible:
!DROOLS-3039.gif|thumbnail!
was (Author: karreiro):
[~jomarko],
Thank you for reporting, however the issue no longer reproducible:
!DROOLS-3039.gif!
> [DMN Designer] Item definition change doesn't make designer dirty
> -----------------------------------------------------------------
>
> Key: DROOLS-3039
> URL: https://issues.jboss.org/browse/DROOLS-3039
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.12.0.Final
> Reporter: Jozef Marko
> Assignee: Guilherme Carreiro
> Priority: Minor
> Labels: drools-tools
> Attachments: DROOLS-3039.gif
>
>
> Changes in item definition definitions don't make the designer dirty. User can then can easily overlook he should save changes before closing the designer.
> h2. Acceptance test
> Check editor is dirty:
> - Definitions moved
> - Definitions declared
> - Definitions removed
> - Definitions edited
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 2 months
[JBoss JIRA] (DROOLS-3039) [DMN Designer] Item definition change doesn't make designer dirty
by Guilherme Carreiro (Jira)
[ https://issues.jboss.org/browse/DROOLS-3039?page=com.atlassian.jira.plugi... ]
Guilherme Carreiro resolved DROOLS-3039.
----------------------------------------
Resolution: Done
> [DMN Designer] Item definition change doesn't make designer dirty
> -----------------------------------------------------------------
>
> Key: DROOLS-3039
> URL: https://issues.jboss.org/browse/DROOLS-3039
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.12.0.Final
> Reporter: Jozef Marko
> Assignee: Guilherme Carreiro
> Priority: Minor
> Labels: drools-tools
> Attachments: DROOLS-3039.gif
>
>
> Changes in item definition definitions don't make the designer dirty. User can then can easily overlook he should save changes before closing the designer.
> h2. Acceptance test
> Check editor is dirty:
> - Definitions moved
> - Definitions declared
> - Definitions removed
> - Definitions edited
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 2 months
[JBoss JIRA] (DROOLS-3039) [DMN Designer] Item definition change doesn't make designer dirty
by Guilherme Carreiro (Jira)
[ https://issues.jboss.org/browse/DROOLS-3039?page=com.atlassian.jira.plugi... ]
Guilherme Carreiro updated DROOLS-3039:
---------------------------------------
Attachment: DROOLS-3039.gif
> [DMN Designer] Item definition change doesn't make designer dirty
> -----------------------------------------------------------------
>
> Key: DROOLS-3039
> URL: https://issues.jboss.org/browse/DROOLS-3039
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.12.0.Final
> Reporter: Jozef Marko
> Assignee: Guilherme Carreiro
> Priority: Minor
> Labels: drools-tools
> Attachments: DROOLS-3039.gif
>
>
> Changes in item definition definitions don't make the designer dirty. User can then can easily overlook he should save changes before closing the designer.
> h2. Acceptance test
> Check editor is dirty:
> - Definitions moved
> - Definitions declared
> - Definitions removed
> - Definitions edited
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 2 months
[JBoss JIRA] (SWSQE-471) Kiali Python Client 0.12
by Matt Mahoney (Jira)
[ https://issues.jboss.org/browse/SWSQE-471?page=com.atlassian.jira.plugin.... ]
Matt Mahoney updated SWSQE-471:
-------------------------------
Sprint: Kiali Sprint #14, Kiali Sprint #16 (was: Kiali Sprint #14, Kiali Sprint #15)
> Kiali Python Client 0.12
> ------------------------
>
> Key: SWSQE-471
> URL: https://issues.jboss.org/browse/SWSQE-471
> Project: Kiali QE
> Issue Type: Story
> Reporter: Matt Mahoney
> Assignee: Michael Foley
> Priority: Major
> Labels: kiali-python-client
>
> Currently there are no tests to validate that the Kiali Python Client is working properly with the Kiali REST API. The purpose of this Story is to get into place a set of tests that validate each of the supported Python Client API methods.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 2 months