View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0005573||SUMo||Bug||public||2019-07-06 14:35||2019-07-21 14:23|
|Priority||normal||Severity||minor||Reproducibility||have not tried|
|Platform||OS||Windows 10 64-bit||OS Version||1809|
|Target Version||Fixed in Version|
|Summary||0005573: Checking and reporting of programs found in exluded folder list|
|Description||After some scan and check operations, I found false positives, detected programs reported as outdated although they're not. A closer look at the path showed that those false positives are found within a backup of some tool. |
Adding this backup path isn't possible via adding button and its explorer of SUMo excluded folder list as this is some Windows user system standard path (AppData). Drag'n Drop though works for such folders in excluded folder list.
After adding this system path to the excluded folder list, I did not ask SUMo for a rescan as I didn't install any new program. I asked SUMo instead to recheck again, expecting that detected programs found in any path added to excluded folder list will no longer be reported neither as up to date nor as outdated.
I observed instead that the list of detected and reported programs didn't shrink, remained with the same count of 4100 programs taking about 830 seconds for checking as scan paths are distributed over PCIe SSD and SATAIII hard disk. And looking for folders of SUMo exclude list in report path of reported outdated tools revealed them present corresponding to the observation of unchanged count of detected and reported tools.
So please fix SUMo behaviour that SUMo excluded folder list doesn't get evaluated just for SUMo scan operations but also for SUMo loading, SUMo checking and SUMo exporting operations.
|Tags||No tags attached.|
The above reported behaviour doesn't seem to persist.
After observing the described behaviour, it remained for several days and check operations. But after more then 48 hours and at least 5 SUMo check actions and several client host reboots, SUMo behaviour turned into expected behaviour. The outdated archived directories are still present. The SUMo exlude list seems to be recognized now. So why not initially?
And why only after a few days? Or which other criteria are triggering this change in behaviour?
This raises also the questions if similar Mantis issues for SUMo scan action and SUMo excluded folder list are persistent or vanish within a few days?
||Correct, if files are ALREADY in the SW list, they're not removed if their parent path gets added to the excluded folders list.|