[JBoss JIRA] (DROOLS-5034) Test scenario grid does not adjust correctly after toggle Test Tools
by Anna Dupliak (Jira)
[ https://issues.redhat.com/browse/DROOLS-5034?page=com.atlassian.jira.plug... ]
Anna Dupliak updated DROOLS-5034:
---------------------------------
Summary: Test scenario grid does not adjust correctly after toggle Test Tools (was: Test scenario grid does not adjust correctly when test scenario openes)
> Test scenario grid does not adjust correctly after toggle Test Tools
> --------------------------------------------------------------------
>
> Key: DROOLS-5034
> URL: https://issues.redhat.com/browse/DROOLS-5034
> Project: Drools
> Issue Type: Bug
> Components: Scenario Simulation and Testing
> Affects Versions: 7.33.0.Final
> Reporter: Anna Dupliak
> Assignee: Yeser Amer
> Priority: Minor
> Labels: drools-tools
> Attachments: Screencast from 02-11-2020.webm, bpms_Traffic-1.zip
>
>
> When user opens grid and scrolls to the edge of table horizontally and hides the Tools Panel then grid is not fitting to the size of the editor. See the [^Screencast from 02-11-2020.webm]
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months
[JBoss JIRA] (DROOLS-5068) Unable to build KieModule with executable model in wildfly
by Mario Fusco (Jira)
[ https://issues.redhat.com/browse/DROOLS-5068?page=com.atlassian.jira.plug... ]
Mario Fusco updated DROOLS-5068:
--------------------------------
Sprint: 2020 Week 07-09 (from Feb 10)
> Unable to build KieModule with executable model in wildfly
> ----------------------------------------------------------
>
> Key: DROOLS-5068
> URL: https://issues.redhat.com/browse/DROOLS-5068
> Project: Drools
> Issue Type: Bug
> Components: core engine
> Affects Versions: 7.32.0.Final
> Reporter: Matteo Casalino
> Assignee: Mario Fusco
> Priority: Major
> Attachments: build-kjar-in-wildfly.zip
>
>
> Building a KieModule with executable model fails when executed in a wildfly container with the following error:
> {noformat}
> Error Messages:
> Message [id=1, level=ERROR, path=src/main/java/org.drools.reproducer/DomainClassesMetadata71E36BCC7D89430EC0E872CFFD5B8B5D.java, line=2, column=44
> text=The type DomainClassesMetadata71E36BCC7D89430EC0E872CFFD5B8B5D collides with a package]
> Message [id=2, level=ERROR, path=src/main/java/org.drools.reproducer/DomainClassesMetadata71E36BCC7D89430EC0E872CFFD5B8B5D.java, line=0, column=0
> text=Java source of src/main/java/org.drools.reproducer/DomainClassesMetadata71E36BCC7D89430EC0E872CFFD5B8B5D.java in error:
> package org.drools.reproducer;
> public class DomainClassesMetadata71E36BCC7D89430EC0E872CFFD5B8B5D {
> public static final org.drools.model.DomainClassMetadata java_lang_String_Metadata_INSTANCE = new java_lang_String_Metadata();
> private static class java_lang_String_Metadata implements org.drools.model.DomainClassMetadata {
> @Override
> public Class<?> getDomainClass() {
> return java.lang.String.class;
> }
> @Override
> public int getPropertiesSize() {
> return 2;
> }
> @Override
> public int getPropertyIndex( String name ) {
> switch(name) {
> case "bytes": return 0;
> case "empty": return 1;
> }
> throw new RuntimeException("Unknown property '" + name + "' for class class class java.lang.String");
> }
> }
> }]
> {noformat}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months
[JBoss JIRA] (DROOLS-5034) Test scenario grid does not adjust correctly when test scenario openes
by Anna Dupliak (Jira)
[ https://issues.redhat.com/browse/DROOLS-5034?page=com.atlassian.jira.plug... ]
Anna Dupliak updated DROOLS-5034:
---------------------------------
Summary: Test scenario grid does not adjust correctly when test scenario openes (was: Test scenario grid does not adjust correctly)
> Test scenario grid does not adjust correctly when test scenario openes
> ----------------------------------------------------------------------
>
> Key: DROOLS-5034
> URL: https://issues.redhat.com/browse/DROOLS-5034
> Project: Drools
> Issue Type: Bug
> Components: Scenario Simulation and Testing
> Affects Versions: 7.33.0.Final
> Reporter: Anna Dupliak
> Assignee: Yeser Amer
> Priority: Major
> Labels: drools-tools
> Attachments: Screencast from 02-11-2020.webm, bpms_Traffic-1.zip
>
>
> When user opens grid and scrolls to the edge of table horizontally and hides the Tools Panel then grid is not fitting to the size of the editor. See the [^Screencast from 02-11-2020.webm]
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months
[JBoss JIRA] (DROOLS-5067) Bound property check mark
by Anna Dupliak (Jira)
[ https://issues.redhat.com/browse/DROOLS-5067?page=com.atlassian.jira.plug... ]
Anna Dupliak updated DROOLS-5067:
---------------------------------
Attachment: ExpressionTick.webm
> Bound property check mark
> -------------------------
>
> Key: DROOLS-5067
> URL: https://issues.redhat.com/browse/DROOLS-5067
> Project: Drools
> Issue Type: Enhancement
> Components: Scenario Simulation and Testing
> Reporter: Jozef Marko
> Assignee: Jozef Marko
> Priority: Trivial
> Labels: drools-tools
> Attachments: ExpressionTick.webm
>
>
> In Test Scenario we have a feature for highlighting a property during binding to a fact property. However we do not highlight the already bound fact property.
> In other words, if a column is bound to some fact property, there should be check mark in test tools panel next to the given fact property.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months
[JBoss JIRA] (DROOLS-5068) Unable to build KieModule with executable model in wildfly
by Matteo Casalino (Jira)
Matteo Casalino created DROOLS-5068:
---------------------------------------
Summary: Unable to build KieModule with executable model in wildfly
Key: DROOLS-5068
URL: https://issues.redhat.com/browse/DROOLS-5068
Project: Drools
Issue Type: Bug
Components: core engine
Affects Versions: 7.32.0.Final
Reporter: Matteo Casalino
Assignee: Mario Fusco
Attachments: build-kjar-in-wildfly.zip
Building a KieModule with executable model fails when executed in a wildfly container with the following error:
{noformat}
Error Messages:
Message [id=1, level=ERROR, path=src/main/java/org.drools.reproducer/DomainClassesMetadata71E36BCC7D89430EC0E872CFFD5B8B5D.java, line=2, column=44
text=The type DomainClassesMetadata71E36BCC7D89430EC0E872CFFD5B8B5D collides with a package]
Message [id=2, level=ERROR, path=src/main/java/org.drools.reproducer/DomainClassesMetadata71E36BCC7D89430EC0E872CFFD5B8B5D.java, line=0, column=0
text=Java source of src/main/java/org.drools.reproducer/DomainClassesMetadata71E36BCC7D89430EC0E872CFFD5B8B5D.java in error:
package org.drools.reproducer;
public class DomainClassesMetadata71E36BCC7D89430EC0E872CFFD5B8B5D {
public static final org.drools.model.DomainClassMetadata java_lang_String_Metadata_INSTANCE = new java_lang_String_Metadata();
private static class java_lang_String_Metadata implements org.drools.model.DomainClassMetadata {
@Override
public Class<?> getDomainClass() {
return java.lang.String.class;
}
@Override
public int getPropertiesSize() {
return 2;
}
@Override
public int getPropertyIndex( String name ) {
switch(name) {
case "bytes": return 0;
case "empty": return 1;
}
throw new RuntimeException("Unknown property '" + name + "' for class class class java.lang.String");
}
}
}]
{noformat}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months
[JBoss JIRA] (JGRP-2451) FD_ALL3
by Bela Ban (Jira)
Bela Ban created JGRP-2451:
------------------------------
Summary: FD_ALL3
Key: JGRP-2451
URL: https://issues.redhat.com/browse/JGRP-2451
Project: JGroups
Issue Type: Feature Request
Reporter: Bela Ban
Assignee: Bela Ban
Fix For: 5.0, 4.2.0
New heartbeat protocol, based on {{FD_ALL2}}.
* Messages should count as heartbeats ({{msg_counts_as_heartbeat}} should be default, and as such, deprecated).
* When a multicast message is sent before {{interval}} elapsed, we suppress sending a heartbeat
* A simple bitmap represents members: bits set to {{1}} mean we received a heartbeat since the last check (at {{timeout}} ms), bits set to {{0}} lead to suspicions
* The bitmap is reset on each check
It is crucial that setting a bit in the bitmap is quick (not like in {{FD_ALL}}, where we fetch the current time from the time service), especially since this is done on every message.
The advantage of {{FD_ALL3}} over previous failure detection protocols is that we only send heartbeats when there is no (multicast) traffic, and we don't suspect a member P when heartbeats have been missing despite receiving traffic from P.
We need to think about whether to consider unicast messages, too, on the sender side: we could populate a bit map with messages sent to members: on a unicast message to P, P's bit would be set in the bit. On a multicast message, all bits would be set. Then, we could selectively send heartbeats only to members with bits set to 0.
However, this is only feasible with sending a message N-1 times (e.g. TCP); for UDP we don't have such an 'anycast' available.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months
[JBoss JIRA] (DROOLS-5051) Mvel type coercion and rounding behavior compatibility between mvel 2.2.8 and 2.4.3
by Toshiya Kobayashi (Jira)
[ https://issues.redhat.com/browse/DROOLS-5051?page=com.atlassian.jira.plug... ]
Toshiya Kobayashi commented on DROOLS-5051:
-------------------------------------------
[~mfusco]
We need to:
- Release mvel 2.4.6.Final
- Let Drools use mvel 2.4.6.Final in the next version
Thanks!
> Mvel type coercion and rounding behavior compatibility between mvel 2.2.8 and 2.4.3
> -----------------------------------------------------------------------------------
>
> Key: DROOLS-5051
> URL: https://issues.redhat.com/browse/DROOLS-5051
> Project: Drools
> Issue Type: Bug
> Components: core engine
> Affects Versions: 7.33.0.Final
> Reporter: Toshiya Kobayashi
> Assignee: Toshiya Kobayashi
> Priority: Major
> Labels: support
>
> I have rule like as:
> =========
> rule "My Rule"
> no-loop true
> dialect "mvel"
> when
> $info : MyInfo()
> then
> modify ($info) {
> setResult(15 * Math.round( new BigDecimal("49.4") ) / 100 )
> }
> end
> =========
> If I execute this rule in BRMS 6.4.x release (mvel 2.2.8), I will get 7.35 in the response . But if I execute same rule in RHDM 7.4.+ release (mvel 2.4.3) I will 7 in the response.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months