| 2016-06-22 12:52:56 |
Alexander Tivelkov |
bug |
|
|
added bug |
| 2016-06-22 12:58:27 |
Alexander Tivelkov |
description |
YAQL has a 'call' function which is capable to run function or method specified by name with a given set of arguments and, when calling methods, a 'receiver' object.
In MuranoPL this function does not work if the receiver object has the class other then the class of the caller. This probably happens because MuranoPL creates a 'method context' for the method calls - and that context include function definitions for the methods of the needed class. When 'call' is called this does not happen and the invocation occurs in the context of the caller. |
YAQL has a 'call' function which is capable to run function or method specified by name with a given set of arguments and, when calling methods, a 'receiver' object.
In MuranoPL this function does not work if the receiver object has the class other then the class of the caller. This probably happens because MuranoPL creates a 'method context' for the method calls - and that context include function definitions for the methods of the needed class. When 'call' is called this does not happen and the invocation occurs in the context of the caller.
See patch https://review.openstack.org/#/c/332792/ for the test demonstrating the bug |
|
| 2016-06-22 13:05:14 |
Alexander Tivelkov |
description |
YAQL has a 'call' function which is capable to run function or method specified by name with a given set of arguments and, when calling methods, a 'receiver' object.
In MuranoPL this function does not work if the receiver object has the class other then the class of the caller. This probably happens because MuranoPL creates a 'method context' for the method calls - and that context include function definitions for the methods of the needed class. When 'call' is called this does not happen and the invocation occurs in the context of the caller.
See patch https://review.openstack.org/#/c/332792/ for the test demonstrating the bug |
YAQL has a 'call' function which is capable to run function or method specified by name with a given set of arguments and, when calling methods, a 'receiver' object.
In MuranoPL this function does not work if the receiver object has the class other then the class of the caller. This probably happens because MuranoPL creates an 'object context' for its calls - and that context include function definitions for the methods of the needed class. When 'call' is called this does not happen and the invocation occurs in the context of the caller.
See patch https://review.openstack.org/#/c/332792/ for the test demonstrating the bug |
|
| 2016-06-22 13:30:54 |
OpenStack Infra |
murano: status |
New |
In Progress |
|
| 2016-06-22 13:30:54 |
OpenStack Infra |
murano: assignee |
|
Alexander Tivelkov (ativelkov) |
|
| 2016-06-22 15:21:40 |
Valerii Kovalchuk |
murano: milestone |
|
newton-2 |
|
| 2016-06-22 15:21:49 |
Valerii Kovalchuk |
murano: importance |
Undecided |
Medium |
|
| 2016-06-23 18:30:12 |
OpenStack Infra |
murano: status |
In Progress |
Fix Released |
|
