[JBoss JIRA] (DROOLS-3451) [DMN Designer] Function: Not possible to select _expression_ cell
by Michael Anstis (Jira)
[ https://issues.jboss.org/browse/DROOLS-3451?page=com.atlassian.jira.plugi... ]
Michael Anstis updated DROOLS-3451:
-----------------------------------
Description:
It is not possible to select the {{FunctionGrid}} _expression_ cell.
Left-single-click does not select cell:
!function-grid-left-click.png|thumbnail!
Whereas right-single-click does (and shows _context_ menu):
!function-grid-right-click.png|thumbnail!
It should be possible to select the cell with single-left-click too.
was:
It is not possible to select the {{FunctionGrid}} _expression_ cell.
Left-single-click does not select cell whereas right-single-click does (and shows _context_ menu).
> [DMN Designer] Function: Not possible to select _expression_ cell
> -----------------------------------------------------------------
>
> Key: DROOLS-3451
> URL: https://issues.jboss.org/browse/DROOLS-3451
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.16.0.Final
> Reporter: Michael Anstis
> Assignee: Daniel José dos Santos
> Priority: Minor
> Labels: drools-tools
> Attachments: function-grid-left-click.png, function-grid-right-click.png
>
>
> It is not possible to select the {{FunctionGrid}} _expression_ cell.
> Left-single-click does not select cell:
> !function-grid-left-click.png|thumbnail!
> Whereas right-single-click does (and shows _context_ menu):
> !function-grid-right-click.png|thumbnail!
> It should be possible to select the cell with single-left-click too.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 9 months
[JBoss JIRA] (DROOLS-3451) [DMN Designer] Function: Not possible to select _expression_ cell
by Michael Anstis (Jira)
Michael Anstis created DROOLS-3451:
--------------------------------------
Summary: [DMN Designer] Function: Not possible to select _expression_ cell
Key: DROOLS-3451
URL: https://issues.jboss.org/browse/DROOLS-3451
Project: Drools
Issue Type: Bug
Components: DMN Editor
Affects Versions: 7.16.0.Final
Reporter: Michael Anstis
Assignee: Daniel José dos Santos
It is not possible to select the {{FunctionGrid}} _expression_ cell.
Left-single-click does not select cell whereas right-single-click does (and shows _context_ menu).
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 9 months
[JBoss JIRA] (DROOLS-3445) Data type constraints: Date
by Liz Clayton (Jira)
[ https://issues.jboss.org/browse/DROOLS-3445?page=com.atlassian.jira.plugi... ]
Liz Clayton commented on DROOLS-3445:
-------------------------------------
[~tirelli] [~karreiro] [~manstis] I have a click-thru proposal that illustrates the three constraint options for "Date" (only): Enumeration, Expression and Range. Please let me know if any features are missing: https://redhat.invisionapp.com/share/D5PPHAI8PAG. Thanks!
> Data type constraints: Date
> ---------------------------
>
> Key: DROOLS-3445
> URL: https://issues.jboss.org/browse/DROOLS-3445
> Project: Drools
> Issue Type: Story
> Components: DMN Editor
> Reporter: Liz Clayton
> Assignee: Liz Clayton
> Priority: Major
> Labels: UX, UXTeam, drools-tools
>
> 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 tab - as a user I want the ability to define constraints for the following types: Date (Expression, Enumeration, and Range.)
> 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)
6 years, 9 months
[JBoss JIRA] (JGRP-2288) S3_PING: Under certain conditions, subclusters fail to merge after network partition
by Nick Sawadsky (Jira)
[ https://issues.jboss.org/browse/JGRP-2288?page=com.atlassian.jira.plugin.... ]
Nick Sawadsky commented on JGRP-2288:
-------------------------------------
[~belaban] Is there an ETA for the 3.6.17 release?
> S3_PING: Under certain conditions, subclusters fail to merge after network partition
> ------------------------------------------------------------------------------------
>
> Key: JGRP-2288
> URL: https://issues.jboss.org/browse/JGRP-2288
> Project: JGroups
> Issue Type: Bug
> Affects Versions: 3.6.15
> Reporter: Nick Sawadsky
> Assignee: Bela Ban
> Priority: Major
> Fix For: 4.0.16, 3.6.17
>
>
> Repro steps:
> 1. Set up a cluster of four nodes, two on one machine (Host 1) and two on another (Host 2). Let's call the nodes A, B, C, and D.
> 2. Configure all 4 nodes with S3_PING as the discovery mechanism. Set remove_all_files_on_view_change to true.
> 3. Start up nodes in the order A, B, C, D.
> 4. In the S3 bucket, there should be a single file with all four nodes listed. Node A should be flagged as the coordinator. Ensure that the UUID for node B is larger than the UUID for node C, when compared as two's complement integers. If this is not the case, shut down all nodes and restart in order. Repeat until the desired relationship is achieved. Note that with two's complement, a UUID having a first hex digit of 8 or higher is treated as negative for comparison purposes. So, for example, a UUID starting with 'a' is less than a UUID starting with 'b' which is less than a UUID starting with '1'.
> 5. On Host 1, use iptables to block all traffic going to and coming from Host 2.
> sudo iptables -A INPUT -s <Host 2 IP addr> -j DROP
> sudo iptables -A OUTPUT -d <Host 2 IP addr> -j DROP
> 6. Allow a few minutes for the nodes to detect the network partition. Eventually you should see two files in the S3 bucket.
> 7. Using Ctrl-C, stop node A.
> 8. You should soon find only a single file in the bucket, containing a single entry for node B. This is a result of the remove_all_files_on_view_change setting on S3_PING, which we set to true to avoid accumulation of old files in the bucket.
> 9. Resolve the network partition:
> sudo iptables -F OUTPUT
> sudo iptables -F INPUT
> 10. You will find that, even after many minutes, the subclusters are not merged.
> I believe the reason why the subclusters are never merged is as follows:
> - MERGE3 on nodes B, C and D uses S3_PING to find members to send INFO messages to. Each one finds only node B in the discovery file. As a result, only node B's view consistency checker has anything to work with.
> - On node B, the consistency checker can see that there are two coordinators, B and C. However, node C has a lower UUID, so node B defers to it to perform the merge. Node C never performs the merge because, as mentioned above, it is not receiving any INFO messages.
> I this this problem would affect FILE_PING as well, and other protocols derived from FILE_PING. Looking at the latest 4.x code, it appears the problem still exists there.
> I think the crux of the issue is that the coordinator on Host 2 (node C) does not re-create its discovery file after it is deleted by node B. Would it be reasonable for FILE_PING.findMembers() to create the discovery file if the node is a coordinator and the file doesn't exist?
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 9 months
[JBoss JIRA] (WFLY-11546) org.jboss.marshalling.reflect.JDKSpecific... uses illegal reflective access
by vbndeveloper (Jira)
vbndeveloper created WFLY-11546:
-----------------------------------
Summary: org.jboss.marshalling.reflect.JDKSpecific... uses illegal reflective access
Key: WFLY-11546
URL: https://issues.jboss.org/browse/WFLY-11546
Project: WildFly
Issue Type: Bug
Components: Remoting
Affects Versions: 15.0.0.Final
Environment: Windows 10, 64-bit
Red Hat (Windows) OpenJDK:
openjdk version "11.0.1" 2018-10-16
OpenJDK Runtime Environment 18.9 (build 11.0.1+13)
OpenJDK 64-Bit Server VM 18.9 (build 11.0.1+13, mixed mode)
Launching within Eclipse RCP OSGi environment where org.jboss.wildfly.client_15.0.0.jar has *Eclipse-BuddyPolicy: registered* MANIFEST.MF entry and plugins that use the remoting have *Eclipse-RegisterBuddy: org.jboss.wildfly.client*.
Reporter: vbndeveloper
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by org.jboss.marshalling.reflect.JDKSpecific$SerMethods (file:/B:/java/rcp/librarires/org.jboss.wildfly.client_15.0.0.jar) to constructor java.util.AbstractMap()
WARNING: Please consider reporting this to the maintainers of org.jboss.marshalling.reflect.JDKSpecific$SerMethods
WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
WARNING: All illegal access operations will be denied in a future release
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 9 months