Bug #2274
Inputs do not correctly detect changes in matches
Start date:
06/25/2018
Due date:
% Done:
100%
Associated revisions
Reorganzing code in to prepare for refactoring code to address bugs
Reference #2274
Fixing issue where the input did not correctly realize that matches hadn't changed
Reference #2274
Adding back logging of the hash
Reference #2274
Fixing logging of the hash value
Reference #2274
Fixed regression that caused result change detecton to fail
Reference #2274
History
#1
Updated by Luke Murphey about 6 years ago
- Target version deleted (
4.5.3)
Observations:
- Input indicates that the result matches don't match but indicates the same new hash. It appears that the hash has changed. It appears that the hash being saved is inconsistent with the one in output_results() versus the one in run().
- Why is the number of results in the repro (with one URL)?
- Should the hashes be deduped?
#2
Updated by Luke Murphey about 6 years ago
- Target version set to 4.5.4
#3
Updated by Luke Murphey about 6 years ago
- Status changed from New to Closed
- % Done changed from 0 to 100
#4
Updated by Luke Murphey about 6 years ago
- Status changed from Closed to In Progress
- % Done changed from 100 to 70
#5
Updated by Luke Murphey about 6 years ago
- Status changed from In Progress to Closed
- % Done changed from 70 to 100