[JBoss JIRA] (DROOLS-5095) [DMN Designer] Investigate performance switching between editor instances
by Michael Biarnes Kiefer (Jira)
[ https://issues.redhat.com/browse/DROOLS-5095?page=com.atlassian.jira.plug... ]
Michael Biarnes Kiefer updated DROOLS-5095:
-------------------------------------------
Fix Version/s: 7.38.0.Final
(was: 7.37.0.Final)
> [DMN Designer] Investigate performance switching between editor instances
> -------------------------------------------------------------------------
>
> Key: DROOLS-5095
> URL: https://issues.redhat.com/browse/DROOLS-5095
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Affects Versions: 7.33.0.Final
> Reporter: Jozef Marko
> Assignee: Guilherme Gomes
> Priority: Minor
> Labels: drools-tools
> Fix For: 7.38.0.Final
>
> Attachments: switch-dmn.webm
>
>
> This JIRA is to investigate the reported performance issue switching between different DMN Designer instances in Business Central.
> The issue was noticed by [~jomarko] when testing DROOLS-5058 (although the fix therein should have had *zero* affect on switching).
> For more details see the video [^switch-dmn.webm]
> h2. Manual acceptance test
> - Prepare 5 DMN models in project
> - Open all in parallel
> - Try to switch between them, keep all opened
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months
[JBoss JIRA] (DROOLS-5230) Managing a List of structures in Test Scenario editor produces an Exception
by Michael Biarnes Kiefer (Jira)
[ https://issues.redhat.com/browse/DROOLS-5230?page=com.atlassian.jira.plug... ]
Michael Biarnes Kiefer updated DROOLS-5230:
-------------------------------------------
Fix Version/s: 7.38.0.Final
(was: 7.37.0.Final)
> 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.38.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, 2 months
[JBoss JIRA] (DROOLS-5252) [DMN Designer] Copy of a imported node shouldn't have a prefix
by Jozef Marko (Jira)
[ https://issues.redhat.com/browse/DROOLS-5252?page=com.atlassian.jira.plug... ]
Jozef Marko resolved DROOLS-5252.
---------------------------------
Fix Version/s: 7.37.0.Final
Resolution: Done
Thank you [~vpellegr]. I think you are right. We can consider this as resolved by DROOLS-5253.
> [DMN Designer] Copy of a imported node shouldn't have a prefix
> --------------------------------------------------------------
>
> Key: DROOLS-5252
> URL: https://issues.redhat.com/browse/DROOLS-5252
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.37.0.Final
> Reporter: Jozef Marko
> Assignee: Valentino Pellegrino
> Priority: Minor
> Labels: drools-tools
> Fix For: 7.37.0.Final
>
> Attachments: imported-node-copy.webm
>
>
> This issue is related to two features of DMN editor.
> - Copy and paste diagram node
> - Nodes of imported model
> If user imported another DMN model into his DMN model, he can use imported nodes in his diagram. They can be easily distinguished by prefix of the imported model. The issue is if we copy and paste such imported node. Created copy has same name as the original node. It is issue because the original-imported one can not be edited while the copy can be edited. Due to the same names it can be confusing why one node can not be edited and the second can be edited.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months
[JBoss JIRA] (DROOLS-5252) [DMN Designer] Copy of a imported node shouldn't have a prefix
by Jozef Marko (Jira)
[ https://issues.redhat.com/browse/DROOLS-5252?page=com.atlassian.jira.plug... ]
Jozef Marko updated DROOLS-5252:
--------------------------------
Description:
This issue is related to two features of DMN editor.
- Copy and paste diagram node
- Nodes of imported model
If user imported another DMN model into his DMN model, he can use imported nodes in his diagram. They can be easily distinguished by prefix of the imported model. The issue is if we copy and paste such imported node. Created copy has same name as the original node. It is issue because the original-imported one can not be edited while the copy can be edited. Due to the same names it can be confusing why one node can not be edited and the second can be edited.
was:
This issue is related to two features of DMN editor.
- Copy and paste diagram node
- Nodes of imported model
If user imported another DMN model into his DMN model, he can use imported nodes in his diagram. They can be easily distinguished by prefix of the imported model. The issue is if we copy and paste such imported node. Created copy shouldn't have the prefix of the original node.
> [DMN Designer] Copy of a imported node shouldn't have a prefix
> --------------------------------------------------------------
>
> Key: DROOLS-5252
> URL: https://issues.redhat.com/browse/DROOLS-5252
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.37.0.Final
> Reporter: Jozef Marko
> Assignee: Valentino Pellegrino
> Priority: Minor
> Labels: drools-tools
> Attachments: imported-node-copy.webm
>
>
> This issue is related to two features of DMN editor.
> - Copy and paste diagram node
> - Nodes of imported model
> If user imported another DMN model into his DMN model, he can use imported nodes in his diagram. They can be easily distinguished by prefix of the imported model. The issue is if we copy and paste such imported node. Created copy has same name as the original node. It is issue because the original-imported one can not be edited while the copy can be edited. Due to the same names it can be confusing why one node can not be edited and the second can be edited.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months
[JBoss JIRA] (DROOLS-5315) "Contains" is not null-safe with executable model
by Matteo Casalino (Jira)
[ https://issues.redhat.com/browse/DROOLS-5315?page=com.atlassian.jira.plug... ]
Matteo Casalino updated DROOLS-5315:
------------------------------------
Description:
When executing rules with executable model, _contains_ constraints are not null-safe, whereas they are in DRL mode
Example of DRL that exhibits the behavior:
{noformat}
rule "contains constraint"
when Pojo(integerList contains 3)
then
end
{noformat}
Error:
{noformat}
java.lang.RuntimeException: java.lang.RuntimeException: java.lang.NullPointerException
at org.drools.modelcompiler.constraints.ConstraintEvaluator.evaluate(ConstraintEvaluator.java:95)
at org.drools.modelcompiler.constraints.LambdaConstraint.isAllowed(LambdaConstraint.java:132)
at org.drools.core.reteoo.AlphaNode.assertObject(AlphaNode.java:139)
at org.drools.core.reteoo.SingleObjectSinkAdapter.propagateAssertObject(SingleObjectSinkAdapter.java:70)
at org.drools.core.reteoo.ObjectTypeNode.propagateAssert(ObjectTypeNode.java:329)
...
{noformat}
The example works fine when running without executable model.
The documentation is not explicit about whether _contains_ should be null safe or not, so we are unsure whether this is to be considered or not a regression.
was:
When executing rules with executable model, _contains _ constraints are not null-safe, whereas they are in DRL mode
Example of DRL that exhibits the behavior:
{noformat}
rule "contains constraint"
when Pojo(integerList contains 3)
then
end
{noformat}
Error:
{noformat}
java.lang.RuntimeException: java.lang.RuntimeException: java.lang.NullPointerException
at org.drools.modelcompiler.constraints.ConstraintEvaluator.evaluate(ConstraintEvaluator.java:95)
at org.drools.modelcompiler.constraints.LambdaConstraint.isAllowed(LambdaConstraint.java:132)
at org.drools.core.reteoo.AlphaNode.assertObject(AlphaNode.java:139)
at org.drools.core.reteoo.SingleObjectSinkAdapter.propagateAssertObject(SingleObjectSinkAdapter.java:70)
at org.drools.core.reteoo.ObjectTypeNode.propagateAssert(ObjectTypeNode.java:329)
...
{noformat}
The example works fine when running without executable model.
The documentation is not explicit about whether _contains _ should be null safe or not, so we are unsure whether this is to be considered or not a regression.
> "Contains" is not null-safe with executable model
> -------------------------------------------------
>
> Key: DROOLS-5315
> URL: https://issues.redhat.com/browse/DROOLS-5315
> Project: Drools
> Issue Type: Bug
> Components: core engine
> Affects Versions: 7.37.0.Final
> Reporter: Matteo Casalino
> Assignee: Mario Fusco
> Priority: Major
> Attachments: null-contains-exec-model.zip
>
>
> When executing rules with executable model, _contains_ constraints are not null-safe, whereas they are in DRL mode
> Example of DRL that exhibits the behavior:
> {noformat}
> rule "contains constraint"
> when Pojo(integerList contains 3)
> then
> end
> {noformat}
> Error:
> {noformat}
> java.lang.RuntimeException: java.lang.RuntimeException: java.lang.NullPointerException
>
> at org.drools.modelcompiler.constraints.ConstraintEvaluator.evaluate(ConstraintEvaluator.java:95)
> at org.drools.modelcompiler.constraints.LambdaConstraint.isAllowed(LambdaConstraint.java:132)
> at org.drools.core.reteoo.AlphaNode.assertObject(AlphaNode.java:139)
> at org.drools.core.reteoo.SingleObjectSinkAdapter.propagateAssertObject(SingleObjectSinkAdapter.java:70)
> at org.drools.core.reteoo.ObjectTypeNode.propagateAssert(ObjectTypeNode.java:329)
> ...
> {noformat}
> The example works fine when running without executable model.
> The documentation is not explicit about whether _contains_ should be null safe or not, so we are unsure whether this is to be considered or not a regression.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months
[JBoss JIRA] (DROOLS-5315) "Contains" is not null-safe with executable model
by Matteo Casalino (Jira)
Matteo Casalino created DROOLS-5315:
---------------------------------------
Summary: "Contains" is not null-safe with executable model
Key: DROOLS-5315
URL: https://issues.redhat.com/browse/DROOLS-5315
Project: Drools
Issue Type: Bug
Components: core engine
Affects Versions: 7.37.0.Final
Reporter: Matteo Casalino
Assignee: Mario Fusco
Attachments: null-contains-exec-model.zip
When executing rules with executable model, _contains _ constraints are not null-safe, whereas they are in DRL mode
Example of DRL that exhibits the behavior:
{noformat}
rule "contains constraint"
when Pojo(integerList contains 3)
then
end
{noformat}
Error:
{noformat}
java.lang.RuntimeException: java.lang.RuntimeException: java.lang.NullPointerException
at org.drools.modelcompiler.constraints.ConstraintEvaluator.evaluate(ConstraintEvaluator.java:95)
at org.drools.modelcompiler.constraints.LambdaConstraint.isAllowed(LambdaConstraint.java:132)
at org.drools.core.reteoo.AlphaNode.assertObject(AlphaNode.java:139)
at org.drools.core.reteoo.SingleObjectSinkAdapter.propagateAssertObject(SingleObjectSinkAdapter.java:70)
at org.drools.core.reteoo.ObjectTypeNode.propagateAssert(ObjectTypeNode.java:329)
...
{noformat}
The example works fine when running without executable model.
The documentation is not explicit about whether _contains _ should be null safe or not, so we are unsure whether this is to be considered or not a regression.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months
[JBoss JIRA] (SWSQE-1143) Solve python2 vs. python3 problem on jenkins slaves
by Filip Brychta (Jira)
[ https://issues.redhat.com/browse/SWSQE-1143?page=com.atlassian.jira.plugi... ]
Filip Brychta edited comment on SWSQE-1143 at 5/11/20 7:46 AM:
---------------------------------------------------------------
This should be done together with SWSQE-836
was (Author: fbrychta):
This should be done together
> Solve python2 vs. python3 problem on jenkins slaves
> ---------------------------------------------------
>
> Key: SWSQE-1143
> URL: https://issues.redhat.com/browse/SWSQE-1143
> Project: Kiali QE
> Issue Type: QE Task
> Reporter: Filip Brychta
> Assignee: Filip Brychta
> Priority: Major
> Labels: infrastructure
>
> Usage of python2 as a default python version on our jenkins slaves causes lot of troubles. It would be good to use python3 everywhere.
> e.g. lot of problem2 with openstack client on python2:
> /usr/lib/python2.7/site-packages/pkg_resources/py2_warn.py:21: UserWarning: Setuptools will stop working on Python 2
> ************************************************************
> You are running Setuptools on Python 2, which is no longer
> supported and
> >>> SETUPTOOLS WILL STOP WORKING <<<
> in a subsequent release (no sooner than 2020-04-20).
> Please ensure you are installing
> Setuptools using pip 9.x or later or pin to `setuptools<45`
> in your environment.
> If you have done those things and are still encountering
> this message, please follow up at
> https://bit.ly/setuptools-py2-warning.
> ************************************************************
> sys.version_info < (3,) and warnings.warn(pre + "*" * 60 + msg + "*" * 60)
> Traceback (most recent call last):
> File "/usr/bin/openstack", line 5, in <module>
> from openstackclient.shell import main
> File "/usr/lib/python2.7/site-packages/openstackclient/shell.py", line 24, in <module>
> from osc_lib import shell
> File "/usr/lib/python2.7/site-packages/osc_lib/shell.py", line 33, in <module>
> from osc_lib.cli import client_config as cloud_config
> File "/usr/lib/python2.7/site-packages/osc_lib/cli/client_config.py", line 18, in <module>
> from openstack.config import exceptions as sdk_exceptions
> File "/usr/lib/python2.7/site-packages/openstack/__init__.py", line 16, in <module>
> import openstack.config
> File "/usr/lib/python2.7/site-packages/openstack/config/__init__.py", line 17, in <module>
> from openstack.config.loader import OpenStackConfig # noqa
> File "/usr/lib/python2.7/site-packages/openstack/config/loader.py", line 33, in <module>
> from openstack.config import cloud_region
> File "/usr/lib/python2.7/site-packages/openstack/config/cloud_region.py", line 44, in <module>
> from openstack import proxy
> File "/usr/lib/python2.7/site-packages/openstack/proxy.py", line 24, in <module>
> from openstack import resource
> File "/usr/lib/python2.7/site-packages/openstack/resource.py", line 49, in <module>
> from openstack import utils
> File "/usr/lib/python2.7/site-packages/openstack/utils.py", line 13, in <module>
> import queue
> ImportError: No module named queue
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months
[JBoss JIRA] (SWSQE-1143) Solve python2 vs. python3 problem on jenkins slaves
by Filip Brychta (Jira)
[ https://issues.redhat.com/browse/SWSQE-1143?page=com.atlassian.jira.plugi... ]
Filip Brychta commented on SWSQE-1143:
--------------------------------------
This should be done together
> Solve python2 vs. python3 problem on jenkins slaves
> ---------------------------------------------------
>
> Key: SWSQE-1143
> URL: https://issues.redhat.com/browse/SWSQE-1143
> Project: Kiali QE
> Issue Type: QE Task
> Reporter: Filip Brychta
> Assignee: Filip Brychta
> Priority: Major
> Labels: infrastructure
>
> Usage of python2 as a default python version on our jenkins slaves causes lot of troubles. It would be good to use python3 everywhere.
> e.g. lot of problem2 with openstack client on python2:
> /usr/lib/python2.7/site-packages/pkg_resources/py2_warn.py:21: UserWarning: Setuptools will stop working on Python 2
> ************************************************************
> You are running Setuptools on Python 2, which is no longer
> supported and
> >>> SETUPTOOLS WILL STOP WORKING <<<
> in a subsequent release (no sooner than 2020-04-20).
> Please ensure you are installing
> Setuptools using pip 9.x or later or pin to `setuptools<45`
> in your environment.
> If you have done those things and are still encountering
> this message, please follow up at
> https://bit.ly/setuptools-py2-warning.
> ************************************************************
> sys.version_info < (3,) and warnings.warn(pre + "*" * 60 + msg + "*" * 60)
> Traceback (most recent call last):
> File "/usr/bin/openstack", line 5, in <module>
> from openstackclient.shell import main
> File "/usr/lib/python2.7/site-packages/openstackclient/shell.py", line 24, in <module>
> from osc_lib import shell
> File "/usr/lib/python2.7/site-packages/osc_lib/shell.py", line 33, in <module>
> from osc_lib.cli import client_config as cloud_config
> File "/usr/lib/python2.7/site-packages/osc_lib/cli/client_config.py", line 18, in <module>
> from openstack.config import exceptions as sdk_exceptions
> File "/usr/lib/python2.7/site-packages/openstack/__init__.py", line 16, in <module>
> import openstack.config
> File "/usr/lib/python2.7/site-packages/openstack/config/__init__.py", line 17, in <module>
> from openstack.config.loader import OpenStackConfig # noqa
> File "/usr/lib/python2.7/site-packages/openstack/config/loader.py", line 33, in <module>
> from openstack.config import cloud_region
> File "/usr/lib/python2.7/site-packages/openstack/config/cloud_region.py", line 44, in <module>
> from openstack import proxy
> File "/usr/lib/python2.7/site-packages/openstack/proxy.py", line 24, in <module>
> from openstack import resource
> File "/usr/lib/python2.7/site-packages/openstack/resource.py", line 49, in <module>
> from openstack import utils
> File "/usr/lib/python2.7/site-packages/openstack/utils.py", line 13, in <module>
> import queue
> ImportError: No module named queue
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months