Nov. 29, 2016
4:17 p.m.
2016-11-29 16:52 GMT+01:00 Yuriy Tymchuk <yuriy.tymchuk@me.com>:
Is there any workaround for this issue? Or maybe someone knows how to fix this. Because the issue is present both in Pharo 5 and the latest Pharo 6.
Probably meta level is not defined somewhere on MetaLink's part. When MetaLink start execution it checks current meta level and if it is higher than where it was installed then link should be ignored. For example recursion could happen if #value:value is used to resolve some #control object and meta level not defined for this part.