[JBoss JIRA] (DROOLS-3032) [DMN Designer] UX "empty" state for custom data types
by Liz Clayton (JIRA)
[ https://issues.jboss.org/browse/DROOLS-3032?page=com.atlassian.jira.plugi... ]
Liz Clayton updated DROOLS-3032:
--------------------------------
Labels: UX UXTeam drools-tools (was: UX drools-tools)
> [DMN Designer] UX "empty" state for custom data types
> -----------------------------------------------------
>
> Key: DROOLS-3032
> URL: https://issues.jboss.org/browse/DROOLS-3032
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Affects Versions: 7.12.0.Final
> Reporter: Liz Clayton
> Assignee: Michael Anstis
> Labels: UX, UXTeam, drools-tools
> Attachments: Screenshot from 2018-09-24 18-12-02.png
>
>
> There is no visual information if no custom data type is defined. In the attached dialog we should differentiate between states when no custom da taype is declared and when some custom data types are declared. The same way we do it in list of spaces and list of projects.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months
[JBoss JIRA] (DROOLS-3032) [DMN Designer] UX "empty" state for custom data types
by Liz Clayton (JIRA)
Liz Clayton created DROOLS-3032:
-----------------------------------
Summary: [DMN Designer] UX "empty" state for custom data types
Key: DROOLS-3032
URL: https://issues.jboss.org/browse/DROOLS-3032
Project: Drools
Issue Type: Task
Components: DMN Editor
Affects Versions: 7.12.0.Final
Reporter: Liz Clayton
Assignee: Michael Anstis
Attachments: Screenshot from 2018-09-24 18-12-02.png
There is no visual information if no custom data type is defined. In the attached dialog we should differentiate between states when no custom da taype is declared and when some custom data types are declared. The same way we do it in list of spaces and list of projects.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months
[JBoss JIRA] (DROOLS-3032) [DMN Designer] UX "empty" state for custom data types
by Liz Clayton (JIRA)
[ https://issues.jboss.org/browse/DROOLS-3032?page=com.atlassian.jira.plugi... ]
Liz Clayton updated DROOLS-3032:
--------------------------------
Story Points: 3
> [DMN Designer] UX "empty" state for custom data types
> -----------------------------------------------------
>
> Key: DROOLS-3032
> URL: https://issues.jboss.org/browse/DROOLS-3032
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Affects Versions: 7.12.0.Final
> Reporter: Liz Clayton
> Assignee: Michael Anstis
> Labels: UX, drools-tools
> Attachments: Screenshot from 2018-09-24 18-12-02.png
>
>
> There is no visual information if no custom data type is defined. In the attached dialog we should differentiate between states when no custom da taype is declared and when some custom data types are declared. The same way we do it in list of spaces and list of projects.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months
[JBoss JIRA] (DROOLS-3027) [DMN Designer] Differentiate zero and non zero custom data types
by Liz Clayton (JIRA)
[ https://issues.jboss.org/browse/DROOLS-3027?page=com.atlassian.jira.plugi... ]
Liz Clayton commented on DROOLS-3027:
-------------------------------------
[~jomarko] Another good catch, yes we should have an empty state for this. I'll make a design story for it.
> [DMN Designer] Differentiate zero and non zero custom data types
> ----------------------------------------------------------------
>
> Key: DROOLS-3027
> URL: https://issues.jboss.org/browse/DROOLS-3027
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Affects Versions: 7.12.0.Final
> Reporter: Jozef Marko
> Assignee: Michael Anstis
> Labels: UX, drools-tools
> Attachments: Screenshot from 2018-09-24 18-12-02.png
>
>
> There is no visual information if no custom data type is defined. In the attached dialog we should differentiate between states when no custom da taype is declared and when some custom data types are declared. The same way we do it in list of spaces and list of projects.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months
[JBoss JIRA] (DROOLS-3028) [DMN Designer] Consolidate data type select boxes
by Liz Clayton (JIRA)
[ https://issues.jboss.org/browse/DROOLS-3028?page=com.atlassian.jira.plugi... ]
Liz Clayton commented on DROOLS-3028:
-------------------------------------
[~jomarko] Thanks, good catch and thanks for filing the jira. [~manstis] Please let me know if you need anything from me, but I'm assuming not at this point.
> [DMN Designer] Consolidate data type select boxes
> -------------------------------------------------
>
> Key: DROOLS-3028
> URL: https://issues.jboss.org/browse/DROOLS-3028
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Affects Versions: 7.12.0.Final
> Reporter: Jozef Marko
> Assignee: Michael Anstis
> Labels: UX, drools-tools
>
> We should consolidate select boxes for data type shown in properties panel and shown in manage custom data type dialog. In the first case we just show ordered default and custom data types. In the second case we add split default and custom data types with headers *DEFAULT* and *CUSTOM*. We should ensure these headers are shown also from properties panel. In other words we should ensure all selectboxes for data type selection have the same look and feel.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months
[JBoss JIRA] (JGRP-2293) Graceful concurrent leaving of coordinator(s) leaves the cluster with stale views
by Radoslav Husar (JIRA)
[ https://issues.jboss.org/browse/JGRP-2293?page=com.atlassian.jira.plugin.... ]
Radoslav Husar commented on JGRP-2293:
--------------------------------------
I don't see use of FD to handle graceful leaving as a viable option (hence this issue). In cloud environments especially where networking is notoriously unreliable, making FD act overly fast could result in false positive cluster splits and making the whole situation even worse. The solution seems to be a proper graceful shutdown, where the coordinator ensures that a successor non-leaving coordinator is elected *and* acknowledged before the node completely shuts down.
> Graceful concurrent leaving of coordinator(s) leaves the cluster with stale views
> ---------------------------------------------------------------------------------
>
> Key: JGRP-2293
> URL: https://issues.jboss.org/browse/JGRP-2293
> Project: JGroups
> Issue Type: Bug
> Affects Versions: 4.0.14
> Reporter: Radoslav Husar
> Assignee: Bela Ban
> Priority: Critical
> Fix For: 4.0.15
>
>
> JGroups does not handle concurrent leaving of nodes correctly. This is a typical use case in cloud environment when scaled down with an autoscaler/manually which we need to handle.
> A simple test can be devised which fails first n (where n>1) nodes from a cluster, reproducer PR https://github.com/belaban/JGroups/pull/397
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months
[JBoss JIRA] (DROOLS-3031) [DMN Designer] UX for Expand / Collapse all
by Liz Clayton (JIRA)
Liz Clayton created DROOLS-3031:
-----------------------------------
Summary: [DMN Designer] UX for Expand / Collapse all
Key: DROOLS-3031
URL: https://issues.jboss.org/browse/DROOLS-3031
Project: Drools
Issue Type: Task
Components: DMN Editor
Affects Versions: 7.12.0.Final
Reporter: Liz Clayton
Assignee: Michael Anstis
User should have possibility to easily expand / collapse all data types in the *manage custom data type* dialog.
h2. Manual acceptance test
- Expand
-- All collapsed initially
-- Something collapsed initially, something expanded already
-- All expanded already
- Collapse
-- All expanded initially
-- Something expanded initially, something collapsed already
-- All collapsed already
- No error warning in browser console log
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months
[JBoss JIRA] (DROOLS-3031) [DMN Designer] UX for Expand / Collapse all
by Liz Clayton (JIRA)
[ https://issues.jboss.org/browse/DROOLS-3031?page=com.atlassian.jira.plugi... ]
Liz Clayton reassigned DROOLS-3031:
-----------------------------------
Assignee: Liz Clayton (was: Michael Anstis)
> [DMN Designer] UX for Expand / Collapse all
> -------------------------------------------
>
> Key: DROOLS-3031
> URL: https://issues.jboss.org/browse/DROOLS-3031
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Affects Versions: 7.12.0.Final
> Reporter: Liz Clayton
> Assignee: Liz Clayton
> Labels: UX, UXTeam, drools-tools
>
> User should have possibility to easily expand / collapse all data types in the *manage custom data type* dialog.
> h2. Manual acceptance test
> - Expand
> -- All collapsed initially
> -- Something collapsed initially, something expanded already
> -- All expanded already
> - Collapse
> -- All expanded initially
> -- Something expanded initially, something collapsed already
> -- All collapsed already
> - No error warning in browser console log
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months
[JBoss JIRA] (DROOLS-3031) [DMN Designer] UX for Expand / Collapse all
by Liz Clayton (JIRA)
[ https://issues.jboss.org/browse/DROOLS-3031?page=com.atlassian.jira.plugi... ]
Liz Clayton updated DROOLS-3031:
--------------------------------
Labels: UX UXTeam drools-tools (was: UX drools-tools)
> [DMN Designer] UX for Expand / Collapse all
> -------------------------------------------
>
> Key: DROOLS-3031
> URL: https://issues.jboss.org/browse/DROOLS-3031
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Affects Versions: 7.12.0.Final
> Reporter: Liz Clayton
> Assignee: Liz Clayton
> Labels: UX, UXTeam, drools-tools
>
> User should have possibility to easily expand / collapse all data types in the *manage custom data type* dialog.
> h2. Manual acceptance test
> - Expand
> -- All collapsed initially
> -- Something collapsed initially, something expanded already
> -- All expanded already
> - Collapse
> -- All expanded initially
> -- Something expanded initially, something collapsed already
> -- All collapsed already
> - No error warning in browser console log
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months
[JBoss JIRA] (WFLY-9447) NPE in ejb client and clean shutdown ERROR [org.jboss.ejb.client.invocation] (default task-8) EJBCLIENT000509: Unexpected exception processing EJB request: java.lang.NullPointerException
by Radoslav Husar (JIRA)
[ https://issues.jboss.org/browse/WFLY-9447?page=com.atlassian.jira.plugin.... ]
Radoslav Husar commented on WFLY-9447:
--------------------------------------
[~tommaso-borgato] The stack trace looks different – are you sure its this issue?
> NPE in ejb client and clean shutdown ERROR [org.jboss.ejb.client.invocation] (default task-8) EJBCLIENT000509: Unexpected exception processing EJB request: java.lang.NullPointerException
> ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: WFLY-9447
> URL: https://issues.jboss.org/browse/WFLY-9447
> Project: WildFly
> Issue Type: Bug
> Components: EJB
> Affects Versions: 14.0.1.Final, 11.0.0.CR1
> Reporter: Radoslav Husar
>
> {noformat}
> ESC[0m13:59:55,004 INFO [org.jboss.as.server] (management-handler-thread - 1) WFLYSRV0211: Suspending server with 15000 ms timeout.
> ESC[0mESC[0m13:59:55,006 INFO [org.jboss.as.ejb3] (management-handler-thread - 1) WFLYEJB0493: EJB subsystem suspension complete
> ESC[0mESC[0m13:59:55,008 INFO [org.jboss.as.server] (Management Triggered Shutdown) WFLYSRV0241: Shutting down in response to management operation 'shutdown'
> ESC[0mESC[0m13:59:55,027 INFO [org.wildfly.extension.undertow] (MSC service thread 1-3) WFLYUT0019: Host default-host stopping
> ESC[0mESC[0m13:59:55,028 INFO [org.jboss.modcluster] (ServerService Thread Pool -- 72) MODCLUSTER000002: Initiating mod_cluster shutdown
> ESC[0mESC[0m13:59:55,039 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-7) ISPN000080: Disconnecting JGroups channel ejb
> ESC[0mESC[0m13:59:55,039 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-1) ISPN000080: Disconnecting JGroups channel ejb
> ESC[0mESC[0m13:59:55,039 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-6) ISPN000080: Disconnecting JGroups channel ejb
> ESC[0mESC[0m13:59:55,040 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-1) ISPN000082: Stopping the RpcDispatcher for channel ejb
> ESC[0mESC[0m13:59:55,040 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-7) ISPN000082: Stopping the RpcDispatcher for channel ejb
> ESC[0mESC[0m13:59:55,040 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-6) ISPN000082: Stopping the RpcDispatcher for channel ejb
> ESC[0mESC[0m13:59:55,042 INFO [org.infinispan.eviction.impl.PassivationManagerImpl] (ServerService Thread Pool -- 74) ISPN000029: Passivating all entries to disk
> ESC[0mESC[0m13:59:55,046 INFO [org.infinispan.eviction.impl.PassivationManagerImpl] (ServerService Thread Pool -- 74) ISPN000030: Passivated 2 entries in 3 milliseconds
> ESC[0mESC[0m13:59:55,055 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-5) WFLYJCA0010: Unbound data source [java:jboss/datasources/ExampleDS]
> ESC[0mESC[0m13:59:55,055 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 74) WFLYCLINF0003: Stopped twocluster-terminus.jar cache from ejb container
> ESC[0m13:59:55,057 DEBUG [org.jboss.ejb.client.invocation] (pool-1-thread-1) Calling invoke(module = /twocluster-forwarder-tx/ForwardingStatefulSBImpl, strong affinity = Cluster "ejb-forwarder", weak affinity = Node "clusterA-node0"):
> ESC[0m13:59:55,059 INFO [org.jboss.as.test.clustering.twoclusters.bean.forwarding.AbstractForwardingStatefulSBImpl] (default task-124) getSerialAndIncrement() called on forwarding node clusterA-node0
> ESC[0mESC[31m13:59:55,062 ERROR [org.jboss.ejb.client.invocation] (default task-8) EJBCLIENT000509: Unexpected exception processing EJB request: java.lang.NullPointerException
> at org.jboss.as.ejb3.deployment.DeploymentRepository.getStartedModules(DeploymentRepository.java:202)
> at org.jboss.as.ejb3.remote.AssociationImpl.findEJB(AssociationImpl.java:382)
> at org.jboss.as.ejb3.remote.AssociationImpl.receiveInvocationRequest(AssociationImpl.java:115)
> at org.jboss.ejb.protocol.remote.EJBServerChannel$ReceiverImpl.handleInvocationRequest(EJBServerChannel.java:450)
> at org.jboss.ejb.protocol.remote.EJBServerChannel$ReceiverImpl.handleMessage(EJBServerChannel.java:188)
> at org.jboss.remoting3.remote.RemoteConnectionChannel.lambda$handleMessageData$3(RemoteConnectionChannel.java:430)
> at org.jboss.remoting3.EndpointImpl$TrackingExecutor.lambda$execute$0(EndpointImpl.java:926)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> {noformat}
> Appears in https://github.com/jbossas/jboss-eap7/pull/2446
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months