Actions
Feature #10929
closedDo not invoke callbacks infinitely and allow to configure the number of iterations
Start date:
09/09/2021
Due date:
% Done:
0%
Estimated time:
Published in build:
Description
One can present examples when bugs will be discovered just after several, perhaps many invocations of callback chains. However, in practice we detect most bugs during a first invocation of callbacks and just a few bugs are revealed during a second iteration. So, I suggest to reduce the number of callback invocations to 2 at most. Moreover, it would be great to have an option to configure that number easily. In many cases users may want to invoke all callbacks one time at most.
Updated by Evgeny Novikov about 3 years ago
- Priority changed from High to Urgent
Updated by Ilja Zakharov about 3 years ago
- Status changed from New to Resolved
Implemented in emg-loop-iterations.
Updated by Evgeny Novikov about 3 years ago
- Status changed from Resolved to Closed
Tests passed, so I merged the branch to master in b4401ac28.
Updated by Evgeny Novikov about 3 years ago
- Related to Feature #11014: Avoid infinite loops in environment models added
Updated by Evgeny Novikov about 3 years ago
- Related to Feature #11015: Describe new abilities in development of environment model specifications added
Actions