Project

General

Profile

Actions

Feature #7965

closed

Do not associate callbacks with verification objects

Added by Evgeny Novikov about 7 years ago. Updated about 7 years ago.

Status:
Closed
Priority:
Urgent
Assignee:
Category:
Environment models
Target version:
-
Start date:
02/09/2017
Due date:
% Done:

0%

Estimated time:
Published in build:

Description

When EMG outputs information about callbacks it associates it with corresponding verification objects each time one particular verification object is specified. Ditto for its input, but there it supports for multiple verification objects and selects the appropriate ones. This is indeed incomplete and dangerous because of callbacks should be associated with all EMG attributes that now include verification objects and rule specifications. These attributes are known without EMG itself, so it shouldn't know and rely of them. When switching off callbacks one should do that not for verification objects, but for sub-jobs where each sub-job should correspond to the only verification object and for one or more rule specifications.

Actions #1

Updated by Evgeny Novikov about 7 years ago

  • Priority changed from High to Urgent

This change is quite trivial while it is absolutely necessary to execute several continues refinements.

Actions #2

Updated by Ilja Zakharov about 7 years ago

  • Status changed from New to Feedback

Implemented in emg-instances-management.

Actions #3

Updated by Evgeny Novikov about 7 years ago

  • Status changed from Feedback to Closed

I merged the branch to master in 6b4cf44. Don't forget to update corresponding jobs!

Actions

Also available in: Atom PDF