Verification reports do not have computational resources in the lightweight mode
I don't know how crucial is this issue (i.e. is this a representation issue or something is wrong at the database level) because of it seems that proper computational resources are shown for all safe/unsafe/unknown reports which are children of verification reports.
Updated by Evgeny Novikov about 3 years ago
- Status changed from Resolved to Closed
I merged the branch to master in 564811c7.
Indeed that wasn't a bug in representation, it was an issue with cache calculation in the lightweight mode. Hopefully, cache recalculation available for in the manager panel helps to get computational resources for verification reports even after they weren't filled correctly originally.