Actions
Bug #8653
closedConfirmed unsafe marks cache is not consistent
Start date:
12/27/2017
Due date:
01/09/2018
% Done:
100%
Estimated time:
Detected in build:
svn
Platform:
Published in build:
Description
If I create a new unsafe mark, then upload a corresponding preset one and then remove the first created mark, an uploaded preset mark is partially confirmed. It isn't confirmed at the unsafe page, but it is confirmed at the job page. Although the use case isn't standard this can point out to a very crucial bug.
Updated by Vladimir Gratinskiy almost 7 years ago
- Due date set to 01/09/2018
- Status changed from New to Resolved
- % Done changed from 0 to 100
Fixed in fix_8653. Corrupted cache can be recalculated on manager tools page (Unsafe marks cache). It can be long as not only confirmed cache is recalculated by clicking this button.
Updated by Evgeny Novikov almost 7 years ago
- Status changed from Resolved to Closed
It helps, so, I merged the branch to master in 2cd89b0.
Actions