New column with item's processing time in a task (#1904)

[wladimirleite]

Closes #1904.

[lfcnassif]

Thank you @tc-wleite! Wouldn't it be better to use evidence ID or evidence object instance itself instead of its path to check if the evidence changed?

[wladimirleite]

Thank you @tc-wleite! Wouldn't it be better to use evidence ID or evidence object instance itself instead of its path to check if the evidence changed?

Yes, I will make this change.

[wladimirleite]

I changed to use the item ID, concatenated with the task name.
It would like to avoid holding any references to these objects.

[lfcnassif]

A while ago I realized this may not work so well with CarverTask because it pauses processing the parent item and process carved items immediately in the same Worker, so the new stat of parent items would be reset several times. Not sure if it is a real problem since the goal is to detect long frozen times executing the exact same job. What do you think @tc-wleite?

[wladimirleite]

A while ago I realized this may not work so well with CarverTask because it pauses processing the parent item and process carved items immediately in the same Worker, so the new stat of parent items would be reset several times. Not sure if it is a real problem since the goal is to detect long frozen times executing the exact same job. What do you think @tc-wleite?

The idea was to present some information about how long a task is running for a given item, without adding any control overhead or modifications in tasks' code.
In the case you mentioned, the column would show how long it is running the carver task since it switched back to the parent item, not the total time, which seems fine to me.

[lfcnassif]

In the case you mentioned, the column would show how long it is running the carver task since it switched back to the parent item, not the total time, which seems fine to me.

Agreed, seems fine to me too given the goal!

without adding any control overhead or modifications in tasks' code.

I noticed this implementation approach (just local changes) and liked it very much! Thank you @tc-wleite!