Open michaelkedar opened 5 days ago
last_update_date gets set to the time when the importer started processing the source
That's at the end of the run, not the start. Does that change your hypothesis at all?
last_update_date gets set to the time when the importer started processing the source
That's at the end of the run, not the start. Does that change your hypothesis at all?
The value is set at the start, but either way, no - there'd be an issue as long as last_import_date
is set anywhere between the two REST updates.
The importer uses
last_update_date
to compare both the Last-Modified of the HEAD request and themodified
time of the individual records.last_update_date
gets set to the time when the importer started processing the source.This can cause an edge case where we miss a few updates:
Here, the importer won't detect the vulnerabilities from the REST source that were modified between
00:10 - 00:15
.