[JBoss JIRA] (DROOLS-5101) rhdm 7 (v 7.5.1; eap 7.2; Drools 7.26; windows 10) FAIL - OutOfMemoryError
by Kris Verlaenen (Jira)
[ https://issues.redhat.com/browse/DROOLS-5101?page=com.atlassian.jira.plug... ]
Kris Verlaenen updated DROOLS-5101:
-----------------------------------
Sprint: 2020 Week 10-12 (from Mar 2), 2020 Week 13-15 (from Mar 23), 2020 Week 16-18 (from Apr 13), 2020 Week 19-21 (from May 4) (was: 2020 Week 10-12 (from Mar 2), 2020 Week 13-15 (from Mar 23), 2020 Week 16-18 (from Apr 13))
> rhdm 7 (v 7.5.1; eap 7.2; Drools 7.26; windows 10) FAIL - OutOfMemoryError
> --------------------------------------------------------------------------
>
> Key: DROOLS-5101
> URL: https://issues.redhat.com/browse/DROOLS-5101
> Project: Drools
> Issue Type: Bug
> Components: core engine
> Affects Versions: 7.26.0.Final
> Reporter: Charles Herrick
> Assignee: Toni Rikkola
> Priority: Critical
>
> 09:13:02,818 ERROR [org.kie.workbench.common.services.backend.builder.core.Builder] (default task-95) GC overhead limit exceeded: java.lang.OutOfMemoryError: GC overhead limit exceeded
> 09:13:05,335 ERROR [stderr] (default task-95) java.lang.OutOfMemoryError: GC overhead limit exceeded
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years
[JBoss JIRA] (DROOLS-4865) Add i18n reporting for DMN V&V
by Kris Verlaenen (Jira)
[ https://issues.redhat.com/browse/DROOLS-4865?page=com.atlassian.jira.plug... ]
Kris Verlaenen updated DROOLS-4865:
-----------------------------------
Sprint: 2020 Week 07-09 (from Feb 10), 2020 Week 10-12 (from Mar 2), 2020 Week 13-15 (from Mar 23), 2020 Week 16-18 (from Apr 13), 2020 Week 19-21 (from May 4) (was: 2020 Week 07-09 (from Feb 10), 2020 Week 10-12 (from Mar 2), 2020 Week 13-15 (from Mar 23), 2020 Week 16-18 (from Apr 13))
> Add i18n reporting for DMN V&V
> ------------------------------
>
> Key: DROOLS-4865
> URL: https://issues.redhat.com/browse/DROOLS-4865
> Project: Drools
> Issue Type: Enhancement
> Components: DMN Editor
> Reporter: Toni Rikkola
> Assignee: Toni Rikkola
> Priority: Major
> Labels: drools-tools
>
> The current reporting from the shared V&V is showing debug messages that are not meant for user to see and the custom DMN V&V is not i18n.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years
[JBoss JIRA] (DROOLS-4575) Test Scenario: unsaved changes warning appears even if file has not been changed
by Kris Verlaenen (Jira)
[ https://issues.redhat.com/browse/DROOLS-4575?page=com.atlassian.jira.plug... ]
Kris Verlaenen updated DROOLS-4575:
-----------------------------------
Sprint: 2020 Week 04-06 (from Jan 20), 2020 Week 07-09 (from Feb 10), 2020 Week 10-12 (from Mar 2), 2020 Week 13-15 (from Mar 23), 2020 Week 16-18 (from Apr 13), 2020 Week 19-21 (from May 4) (was: 2020 Week 04-06 (from Jan 20), 2020 Week 07-09 (from Feb 10), 2020 Week 10-12 (from Mar 2), 2020 Week 13-15 (from Mar 23), 2020 Week 16-18 (from Apr 13))
> Test Scenario: unsaved changes warning appears even if file has not been changed
> --------------------------------------------------------------------------------
>
> Key: DROOLS-4575
> URL: https://issues.redhat.com/browse/DROOLS-4575
> Project: Drools
> Issue Type: Bug
> Components: Scenario Simulation and Testing
> Reporter: Daniele Zonca
> Assignee: Daniele Zonca
> Priority: Major
> Labels: CustomerFocus, drools-tools
>
> If user opens a scesim file and then close it, no confirmation message should be opened
> h2. Manual Acceptance Test
> - Opening and closing without changes
> - Open, change data in cell, close
> - Open, add column, remove column, change column binding, close
> - Open, Change settings on the settings panel (e.g. ruleflow group, kie session), close
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years
[JBoss JIRA] (DROOLS-5193) Implement Listener mechanism to trace execution
by Kris Verlaenen (Jira)
[ https://issues.redhat.com/browse/DROOLS-5193?page=com.atlassian.jira.plug... ]
Kris Verlaenen updated DROOLS-5193:
-----------------------------------
Sprint: 2020 Week 13-15 (from Mar 23), 2020 Week 16-18 (from Apr 13), 2020 Week 19-21 (from May 4) (was: 2020 Week 13-15 (from Mar 23), 2020 Week 16-18 (from Apr 13))
> Implement Listener mechanism to trace execution
> -----------------------------------------------
>
> Key: DROOLS-5193
> URL: https://issues.redhat.com/browse/DROOLS-5193
> Project: Drools
> Issue Type: Task
> Reporter: Gabriele Cardosi
> Assignee: Gabriele Cardosi
> Priority: Major
> Labels: TrustyAI
>
> Implement Listener architecture so that model-implementation may "publish" execution step detail to be read by "listening" code.
> Implementation should not be mandatory, i.e. model should not be forced to implement it.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years
[JBoss JIRA] (DROOLS-2845) Extend the existing verifier to support DMN tables
by Kris Verlaenen (Jira)
[ https://issues.redhat.com/browse/DROOLS-2845?page=com.atlassian.jira.plug... ]
Kris Verlaenen updated DROOLS-2845:
-----------------------------------
Sprint: 2019 Week 47-49 (from Nov 18), 2019 Week 50-52 (from Dec 9), 2020 Week 01-03 (from Dec 30), 2020 Week 04-06 (from Jan 20), 2020 Week 07-09 (from Feb 10), 2020 Week 10-12 (from Mar 2), 2020 Week 13-15 (from Mar 23), 2020 Week 16-18 (from Apr 13), 2020 Week 19-21 (from May 4) (was: 2019 Week 47-49 (from Nov 18), 2019 Week 50-52 (from Dec 9), 2020 Week 01-03 (from Dec 30), 2020 Week 04-06 (from Jan 20), 2020 Week 07-09 (from Feb 10), 2020 Week 10-12 (from Mar 2), 2020 Week 13-15 (from Mar 23), 2020 Week 16-18 (from Apr 13))
> Extend the existing verifier to support DMN tables
> --------------------------------------------------
>
> Key: DROOLS-2845
> URL: https://issues.redhat.com/browse/DROOLS-2845
> Project: Drools
> Issue Type: Epic
> Components: DMN Editor, verifier
> Reporter: Toni Rikkola
> Assignee: Toni Rikkola
> Priority: Optional
> Labels: UX, drools-tools, verifier
>
> h1. Goal
> Merge the Validation methods DMN has with the generic Validator that is used by the GDST.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years
[JBoss JIRA] (DROOLS-4562) DMN validation semantic rules for DMNDI
by Kris Verlaenen (Jira)
[ https://issues.redhat.com/browse/DROOLS-4562?page=com.atlassian.jira.plug... ]
Kris Verlaenen updated DROOLS-4562:
-----------------------------------
Sprint: 2020 Week 13-15 (from Mar 23), 2020 Week 16-18 (from Apr 13), 2020 Week 19-21 (from May 4) (was: 2020 Week 13-15 (from Mar 23), 2020 Week 16-18 (from Apr 13))
> DMN validation semantic rules for DMNDI
> ---------------------------------------
>
> Key: DROOLS-4562
> URL: https://issues.redhat.com/browse/DROOLS-4562
> Project: Drools
> Issue Type: Enhancement
> Components: dmn engine
> Reporter: Matteo Mortari
> Assignee: Toshiya Kobayashi
> Priority: Major
> Labels: good-first-issue
>
> Provide rules for the -validator module which can semantically inspect the DMNDI element to ensure the minimal requirements from the DMN specification are (semantically) respected in the .dmn xml file.
> These rules can be implemented in the subset of the KB for the DMN v1.2 and greater, to leverage use of the standard DMNDI elements.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years
[JBoss JIRA] (DROOLS-5230) Managing a List of structures in Test Scenario editor produces an Exception
by Kris Verlaenen (Jira)
[ https://issues.redhat.com/browse/DROOLS-5230?page=com.atlassian.jira.plug... ]
Kris Verlaenen updated DROOLS-5230:
-----------------------------------
Sprint: 2020 Week 16-18 (from Apr 13), 2020 Week 19-21 (from May 4) (was: 2020 Week 16-18 (from Apr 13))
> Managing a List of structures in Test Scenario editor produces an Exception
> ---------------------------------------------------------------------------
>
> Key: DROOLS-5230
> URL: https://issues.redhat.com/browse/DROOLS-5230
> Project: Drools
> Issue Type: Bug
> Components: Scenario Simulation and Testing
> Affects Versions: 7.34.0.Final
> Reporter: Tracy Hires
> Assignee: Yeser Amer
> Priority: Critical
> Fix For: 7.37.0.Final
>
> Attachments: Error screen shot.png, test_scenario_list_exception.zip
>
>
> When trying to delete an item from a list of structures with nested structures in the scenario editor, an exception is thrown with a message that is not helpful to the end user.
> Log entry is:
> ```
> ^[[0m^[[31m17:16:51,564 ERROR [org.kie.workbench.common.services.backend.logger.GenericErrorLoggerServiceImpl] (default task-415) Error from user: xxxxx Error ID: -881202734 Location: LibraryPerspective|$ProjectScreen[!Worg.kie.dmn.decision.navigator,EDiagramEditorPropertiesScreen,Eorg.drools.scenariosimulation.TestTools?scesimeditorid=1,!Eorg.drools.scenariosimulation.TestTools?scesimeditorid=2,Eorg.docks.PlaceHolder?name=testRunnerReportingPanel,Worg.kie.guvnor.explorer,],DMNDiagramEditor?path_uri=default://master@dm-ai/XmlValidationBug/src/main/resources/Math%2520Functions.dmn&file_name=Math%20Functions.dmn&has_version_support=true,DMNDiagramEditor?path_uri=default://master@dm-ai/XmlValidationBug/src/main/resources/Divide.dmn&file_name=Divide.dmn&has_version_support=true,org.kie.workbench.common.screens.messageconsole.MessageConsole,,AddAssetsScreen,ScenarioSimulationEditor?path_uri=default://master@dm-ai/XmlValidationBug/src/test/resources/Test%2520Math%2520Functions.scesim&file_name=Test%20Math%20Functions.scesim&has_version_support=true Exception: Uncaught exception: Exception caught: (TypeError) : Cannot read property 'Tc' of undefined Caused by: (TypeError) : Cannot read property 'Tc' of undefined
> ```
> From UI I could see: `Uncaught exception: Exception caught: (TypeError) : Cannot read property 'Tc' of undefined Caused by: (TypeError) : Cannot read property 'Tc' of undefined`
> (Screenshot is attached)
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years