[JBoss JIRA] (DROOLS-5291) Import of empty scesim file leads to Unexpected error
by Anna Dupliak (Jira)
[ https://issues.redhat.com/browse/DROOLS-5291?page=com.atlassian.jira.plug... ]
Anna Dupliak edited comment on DROOLS-5291 at 5/4/20 6:12 AM:
--------------------------------------------------------------
[~yamer]
Indeed the error appears independently on where the file have been created. This seems like a bug in Business central. If you import an empty scesim then it throws unexpected error.
was (Author: adupliak):
[~yamer]
Indeed the error appears independently on where the file have been created. This seems like a bug in Business central. If you import an empty scesim then it will throw unexpected error.
> Import of empty scesim file leads to Unexpected error
> -----------------------------------------------------
>
> Key: DROOLS-5291
> URL: https://issues.redhat.com/browse/DROOLS-5291
> Project: Drools
> Issue Type: Bug
> Components: Scenario Simulation and Testing
> Affects Versions: 7.36.0.Final
> Reporter: Anna Dupliak
> Assignee: Yeser Amer
> Priority: Minor
> Labels: drools-tools, kogito-tooling
> Attachments: Traffic.zip, errorlog.txt, image-2020-04-17-16-47-29-261.png, image-2020-04-17-16-47-32-047.png
>
>
> If user generate a scesim file using vs code extention it is not comparable with BC.
> Use Vscode generated files [^Traffic.zip]
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
3 years, 11 months
[JBoss JIRA] (DROOLS-5291) Import of empty scesim file leads to Unexpected error
by Anna Dupliak (Jira)
[ https://issues.redhat.com/browse/DROOLS-5291?page=com.atlassian.jira.plug... ]
Anna Dupliak updated DROOLS-5291:
---------------------------------
Steps to Reproduce:
# Import empty file with scesim extention
# Expected test scenario editor is opened and ready to work
# Actual !image-2020-04-17-16-47-32-047.png|thumbnail!
# See the error [^errorlog.txt]
was:
# Import TraficViolation.dmn from the archive [^Traffic.zip] to BC
# Import TrafficViolationTest.scesim from the archive [^Traffic.zip] to BC
# Expected test scenario editor is opened and ready to work
# Actual !image-2020-04-17-16-47-32-047.png|thumbnail!
# See the error [^errorlog.txt]
> Import of empty scesim file leads to Unexpected error
> -----------------------------------------------------
>
> Key: DROOLS-5291
> URL: https://issues.redhat.com/browse/DROOLS-5291
> Project: Drools
> Issue Type: Bug
> Components: Scenario Simulation and Testing
> Affects Versions: 7.36.0.Final
> Reporter: Anna Dupliak
> Assignee: Yeser Amer
> Priority: Minor
> Labels: drools-tools, kogito-tooling
> Attachments: Traffic.zip, errorlog.txt, image-2020-04-17-16-47-29-261.png, image-2020-04-17-16-47-32-047.png
>
>
> If user generate a scesim file using vs code extention it is not comparable with BC.
> Use Vscode generated files [^Traffic.zip]
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
3 years, 11 months
[JBoss JIRA] (DROOLS-5291) Import of empty scesim file leads to Unexpected error
by Anna Dupliak (Jira)
[ https://issues.redhat.com/browse/DROOLS-5291?page=com.atlassian.jira.plug... ]
Anna Dupliak updated DROOLS-5291:
---------------------------------
Summary: Import of empty scesim file leads to Unexpected error (was: Scesim file generated by VS code extention brings Unexpected error when user opens it in Business Central)
> Import of empty scesim file leads to Unexpected error
> -----------------------------------------------------
>
> Key: DROOLS-5291
> URL: https://issues.redhat.com/browse/DROOLS-5291
> Project: Drools
> Issue Type: Bug
> Components: Scenario Simulation and Testing
> Affects Versions: 7.36.0.Final
> Reporter: Anna Dupliak
> Assignee: Yeser Amer
> Priority: Minor
> Labels: drools-tools, kogito-tooling
> Attachments: Traffic.zip, errorlog.txt, image-2020-04-17-16-47-29-261.png, image-2020-04-17-16-47-32-047.png
>
>
> If user generate a scesim file using vs code extention it is not comparable with BC.
> Use Vscode generated files [^Traffic.zip]
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
3 years, 11 months
[JBoss JIRA] (DROOLS-5291) Scesim file generated by VS code extention brings Unexpected error when user opens it in Business Central
by Anna Dupliak (Jira)
[ https://issues.redhat.com/browse/DROOLS-5291?page=com.atlassian.jira.plug... ]
Anna Dupliak moved KOGITO-1902 to DROOLS-5291:
----------------------------------------------
Project: Drools (was: Kogito)
Key: DROOLS-5291 (was: KOGITO-1902)
Docs QE Status: NEW
Component/s: Scenario Simulation and Testing
(was: Scenario Simulation)
Affects Version/s: 7.36.0.Final
(was: Kogito Tooling 0.4.2)
QE Status: NEW
> Scesim file generated by VS code extention brings Unexpected error when user opens it in Business Central
> ---------------------------------------------------------------------------------------------------------
>
> Key: DROOLS-5291
> URL: https://issues.redhat.com/browse/DROOLS-5291
> Project: Drools
> Issue Type: Bug
> Components: Scenario Simulation and Testing
> Affects Versions: 7.36.0.Final
> Reporter: Anna Dupliak
> Assignee: Yeser Amer
> Priority: Major
> Labels: drools-tools, kogito-tooling
> Attachments: Traffic.zip, errorlog.txt, image-2020-04-17-16-47-29-261.png, image-2020-04-17-16-47-32-047.png
>
>
> If user generate a scesim file using vs code extention it is not comparable with BC.
> Use Vscode generated files [^Traffic.zip]
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
3 years, 11 months
[JBoss JIRA] (DROOLS-5290) Executable model compiled throws exception in accumulate pattern matching
by Luca Molteni (Jira)
Luca Molteni created DROOLS-5290:
------------------------------------
Summary: Executable model compiled throws exception in accumulate pattern matching
Key: DROOLS-5290
URL: https://issues.redhat.com/browse/DROOLS-5290
Project: Drools
Issue Type: Bug
Components: executable model
Reporter: Luca Molteni
Assignee: Luca Molteni
Customer is encountering below issue while rule execution if they use executable model.
{code:java}
Exception in thread "main" java.lang.RuntimeException: java.lang.ClassCastException: org.drools.core.reteoo.SubnetworkTuple
cannot be cast to java.lang.Long
at org.drools.core.rule.SingleAccumulate.accumulate(SingleAccumulate.java:105)
at org.drools.core.phreak.PhreakAccumulateNode.addMatch(PhreakAccumulateNode.java:714)
at org.drools.core.phreak.PhreakAccumulateNode.doLeftInserts(PhreakAccumulateNode.java:168)
at org.drools.core.phreak.PhreakAccumulateNode.doNode(PhreakAccumulateNode.java:89)
at org.drools.core.phreak.RuleNetworkEvaluator.switchOnDoBetaNode(RuleNetworkEvaluator.java:581)
at org.drools.core.phreak.RuleNetworkEvaluator.evalBetaNode(RuleNetworkEvaluator.java:552)
at org.drools.core.phreak.RuleNetworkEvaluator.evalNode(RuleNetworkEvaluator.java:379)
at org.drools.core.phreak.RuleNetworkEvaluator.innerEval(RuleNetworkEvaluator.java:339)
at org.drools.core.phreak.RuleNetworkEvaluator.evalStackEntry(RuleNetworkEvaluator.java:237)
at org.drools.core.phreak.RuleNetworkEvaluator.outerEval(RuleNetworkEvaluator.java:180)
{code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
3 years, 11 months
[JBoss JIRA] (DROOLS-4891) Further Optimize Lambdas in Executable Model
by Luca Molteni (Jira)
[ https://issues.redhat.com/browse/DROOLS-4891?page=com.atlassian.jira.plug... ]
Luca Molteni updated DROOLS-4891:
---------------------------------
Sprint: 2020 Week 10-12 (from Mar 2), 2020 Week 13-15 (from Mar 23) (was: 2020 Week 10-12 (from Mar 2), 2020 Week 13-15 (from Mar 23), 2020 Week 16-18 (from Apr 13))
> Further Optimize Lambdas in Executable Model
> --------------------------------------------
>
> Key: DROOLS-4891
> URL: https://issues.redhat.com/browse/DROOLS-4891
> Project: Drools
> Issue Type: Enhancement
> Reporter: Luca Molteni
> Assignee: Luca Molteni
> Priority: Major
> Labels: good-first-issue
>
> Lambda shouldn't be externalized depending on the variable name but on the actual lambda.
> So
> person.name == a
> person.name == b
> Is effectively the same lambda and should externalized once.
> Hint: we could rename the parameters to p1, p2, p3, promote the types to fully qualified names and get this result.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
3 years, 11 months