[JBoss JIRA] (DROOLS-2603) Stunner: Single Node Selection
by Michael Anstis (Jira)
[ https://issues.jboss.org/browse/DROOLS-2603?page=com.atlassian.jira.plugi... ]
Michael Anstis updated DROOLS-2603:
-----------------------------------
Summary: Stunner: Single Node Selection (was: [DMN Designer] Single Node Selection)
> Stunner: Single Node Selection
> ------------------------------
>
> Key: DROOLS-2603
> URL: https://issues.jboss.org/browse/DROOLS-2603
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.8.0.Final
> Reporter: Jozef Marko
> Assignee: Roger Martinez
> Priority: Minor
> Attachments: DROOLS-2603.gif, Screenshot from 2018-05-30 09-10-26.png
>
>
> If user selects multiple nodes on canvas (blue rectangle around them) and then select single node in the navigation dock, the group selection will not disappear, see the attachment.
> It is not consistent with selecting single node directly on canvas, that always discards the group selection (if present).
> h3. Manual Acceptance test
> Prerequisite: Select group of nodes
> - Select single by click on canvas
> - Select single by click in navigation dock
> - Open some context editor, just return to canvas with *Back to xyz*
> - Open some context editor, return to canvas by click in navigation dock
> - Select single by click in process explorer
> - Try to select different group on canvas
> - Move a node that doesn't belong to the selected group
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 8 months
[JBoss JIRA] (DROOLS-2603) Stunner: Single Node Selection
by Michael Anstis (Jira)
[ https://issues.jboss.org/browse/DROOLS-2603?page=com.atlassian.jira.plugi... ]
Michael Anstis updated DROOLS-2603:
-----------------------------------
Component/s: Stunner
(was: DMN Editor)
> Stunner: Single Node Selection
> ------------------------------
>
> Key: DROOLS-2603
> URL: https://issues.jboss.org/browse/DROOLS-2603
> Project: Drools
> Issue Type: Bug
> Components: Stunner
> Affects Versions: 7.8.0.Final
> Reporter: Jozef Marko
> Assignee: Roger Martinez
> Priority: Minor
> Attachments: DROOLS-2603.gif, Screenshot from 2018-05-30 09-10-26.png
>
>
> If user selects multiple nodes on canvas (blue rectangle around them) and then select single node in the navigation dock, the group selection will not disappear, see the attachment.
> It is not consistent with selecting single node directly on canvas, that always discards the group selection (if present).
> h3. Manual Acceptance test
> Prerequisite: Select group of nodes
> - Select single by click on canvas
> - Select single by click in navigation dock
> - Open some context editor, just return to canvas with *Back to xyz*
> - Open some context editor, return to canvas by click in navigation dock
> - Select single by click in process explorer
> - Try to select different group on canvas
> - Move a node that doesn't belong to the selected group
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 8 months
[JBoss JIRA] (REMJMX-153) Remoting "endpoint" threads not existing after application stopped
by Yeray Borges (Jira)
[ https://issues.jboss.org/browse/REMJMX-153?page=com.atlassian.jira.plugin... ]
Yeray Borges resolved REMJMX-153.
---------------------------------
Resolution: Out of Date
> Remoting "endpoint" threads not existing after application stopped
> ------------------------------------------------------------------
>
> Key: REMJMX-153
> URL: https://issues.jboss.org/browse/REMJMX-153
> Project: Remoting JMX
> Issue Type: Bug
> Affects Versions: 2.0.1.Final
> Environment: - EAP 7.0.z
> - JDK 8
> Reporter: Yeray Borges
> Assignee: Yeray Borges
> Priority: Major
>
> Customer wrote a monitoring tool for JBoss which uses JMX, his env is EAP 7.0.6. When the jmx url is set to an invalid port, we are noticing the number of threads growing in EAP as the test run over the time. I can replicate his issue on my machine. The threads are
> "Remoting "endpoint" I/O-1"
> "Remoting "endpoint" task-1"
> "Remoting "endpoint" Accept"
> For example:
> "Remoting "endpoint" Accept" #878 daemon prio=5 os_prio=0 tid=0x00007fe6dc1cf800 nid=0x4c2f runnable [0x00007fe66fbfe000]
> java.lang.Thread.State: RUNNABLE
> at sun.nio.ch.EPollArrayWrapper.epollWait(Native Method)
> at sun.nio.ch.EPollArrayWrapper.poll(EPollArrayWrapper.java:269)
> at sun.nio.ch.EPollSelectorImpl.doSelect(EPollSelectorImpl.java:93)
> at sun.nio.ch.SelectorImpl.lockAndDoSelect(SelectorImpl.java:86)
> - locked <0x00000000e6f3a1f8> (a sun.nio.ch.Util$3)
> - locked <0x00000000e6f3a1e8> (a java.util.Collections$UnmodifiableSet)
> - locked <0x00000000e6f3a0d0> (a sun.nio.ch.EPollSelectorImpl)
> at sun.nio.ch.SelectorImpl.select(SelectorImpl.java:97)
> at sun.nio.ch.SelectorImpl.select(SelectorImpl.java:101)
> at org.xnio.nio.WorkerThread.run(WorkerThread.java:515)
> for the 200 loop, I can see 798 live threads, and 616 Daemon threads in JBoss.
> The test scripts are:
> run_test.sh is
> for i in {1..200}; do curl -H "Content-Type: application/json" -X POST --data-binary "@jbmonitorRequestdata.txt" test1.redhat.com:8080/infra.jbossmonitor-0.0.4/beaninfo; done
> and the jbmonitorRequestdata.txt is
> [
> {
> "user": "admin",
> "password": "password",
> "url": "service:jmx:remote+http://test1.redhat.com:1990",
> "measurements": {
> "jboss_web_ajp": "jboss.as:subsystem=web,connector=ajp",
> "jboss_web_http": "jboss.as:subsystem=web,connector=http",
> "jboss_datasource": "jboss.as:subsystem=datasources,data-source=*,statistics=pool"
> },
> "tags": {
> "host": "test1.redhat.com",
> "application": "apiplatform",
> "env": "dev"
> }
> }
> ]
> I will attach the customer code to this jira
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 8 months
[JBoss JIRA] (DROOLS-4767) Fix error-popover position on simulation/background grids
by Gabriele Cardosi (Jira)
Gabriele Cardosi created DROOLS-4767:
----------------------------------------
Summary: Fix error-popover position on simulation/background grids
Key: DROOLS-4767
URL: https://issues.jboss.org/browse/DROOLS-4767
Project: Drools
Issue Type: Bug
Components: Scenario Simulation and Testing
Reporter: Gabriele Cardosi
Assignee: Gabriele Cardosi
When there is only one column on the grid, the popover is show to the left. But if there is not enough space to the left, the popover is not visible.
Proposed solution, for this situation, is to show the popover _below_ the cell.
If there is not space below, the the popover will be shown _above_.
The final position preference order will be (respect the cell):
RIGTH -> LEFT -> BELOW -> ABOVE
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 8 months
[JBoss JIRA] (DROOLS-3264) [DMN Designer] Improve popover interaction
by Michael Anstis (Jira)
[ https://issues.jboss.org/browse/DROOLS-3264?page=com.atlassian.jira.plugi... ]
Michael Anstis resolved DROOLS-3264.
------------------------------------
Resolution: Out of Date
> [DMN Designer] Improve popover interaction
> ------------------------------------------
>
> Key: DROOLS-3264
> URL: https://issues.jboss.org/browse/DROOLS-3264
> Project: Drools
> Issue Type: Enhancement
> Components: DMN Editor
> Reporter: Guilherme Gomes
> Assignee: Michael Anstis
> Priority: Minor
> Labels: drools-tools
> Attachments: popover.png
>
>
> When this popover is opened:
> !popover.png|thumbnail!
> ..the first input is not being focused.
> The expected behaviour is to focus the input (name input) when the popover is opened.
> h2. Acceptance test
> Immediately after popover is shown, user isa able to change the name without any additional clicks to put focus to some input field
> - Firefox
> - Chrome
> - Edge
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 8 months
[JBoss JIRA] (DROOLS-3264) [DMN Designer] Improve popover interaction
by Michael Anstis (Jira)
[ https://issues.jboss.org/browse/DROOLS-3264?page=com.atlassian.jira.plugi... ]
Michael Anstis commented on DROOLS-3264:
----------------------------------------
Setting this issue to {{Resolved}} as the first item now receives the focus _in most scenarios_.
The linked JIRA covers one inconsistency.
> [DMN Designer] Improve popover interaction
> ------------------------------------------
>
> Key: DROOLS-3264
> URL: https://issues.jboss.org/browse/DROOLS-3264
> Project: Drools
> Issue Type: Enhancement
> Components: DMN Editor
> Reporter: Guilherme Gomes
> Assignee: Michael Anstis
> Priority: Minor
> Labels: drools-tools
> Attachments: popover.png
>
>
> When this popover is opened:
> !popover.png|thumbnail!
> ..the first input is not being focused.
> The expected behaviour is to focus the input (name input) when the popover is opened.
> h2. Acceptance test
> Immediately after popover is shown, user isa able to change the name without any additional clicks to put focus to some input field
> - Firefox
> - Chrome
> - Edge
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 8 months
[JBoss JIRA] (DROOLS-2583) [DMN Designer] Type Ref select box keyboard control
by Michael Anstis (Jira)
[ https://issues.jboss.org/browse/DROOLS-2583?page=com.atlassian.jira.plugi... ]
Michael Anstis resolved DROOLS-2583.
------------------------------------
Resolution: Duplicate Issue
> [DMN Designer] Type Ref select box keyboard control
> ---------------------------------------------------
>
> Key: DROOLS-2583
> URL: https://issues.jboss.org/browse/DROOLS-2583
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Reporter: Jozef Marko
> Assignee: Michael Anstis
> Priority: Optional
> Labels: drools-tools
> Attachments: Screenshot from 2018-05-23 11-31-01.png
>
>
> Common HTML select boxes can be controlled by keyboard. KeyPress of the Arrow.DOWN or Arrow.UP moves one option one or down. This is not true for Type Ref select box. There by pressing Arrow.DOWN or Arrow.UP user is able to select just every second option.
> Attaching screenshot of the select box just for record which select box I mean.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 8 months
[JBoss JIRA] (DROOLS-3120) [DMN Designer] Validation Error State remains active
by Michael Anstis (Jira)
[ https://issues.jboss.org/browse/DROOLS-3120?page=com.atlassian.jira.plugi... ]
Michael Anstis commented on DROOLS-3120:
----------------------------------------
[~jomarko] I re-tested this with {{master}} (as at 15 November 2019) and can no longer replicate.
This would have been a Stunner issue however I suspect something somewhere in Stunner has since resolved this issue.
When you're next using the editor can you please re-test and close this if possible.
> [DMN Designer] Validation Error State remains active
> ----------------------------------------------------
>
> Key: DROOLS-3120
> URL: https://issues.jboss.org/browse/DROOLS-3120
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.13.0.Final
> Reporter: Jozef Marko
> Assignee: Michael Anstis
> Priority: Optional
> Labels: drools-tools
> Attachments: Screenshot from 2018-10-11 17-50-01.png
>
>
> The is sequence of steps the error validation state of node remains active. It is shown in the attachment.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 8 months