summaryrefslogtreecommitdiffstats
path: root/api/examples
diff options
context:
space:
mode:
authorKotresh HR <khiremat@redhat.com>2018-08-21 06:09:44 -0400
committerAmar Tumballi <amarts@redhat.com>2018-08-31 13:28:43 +0000
commit35aa67001c8fac99b040fbc61f36ef4f1b1590ac (patch)
tree2d0e75b469b37738a7a61c2171aadc5a58956b5d /api/examples
parent052849983e51a061d7fb2c3ffd74fa78bb257084 (diff)
libgfchangelog: Fix changelog history API
Problem: If requested start time and end time doesn't fall into first HTIME file, then history API fails even though continuous changelogs are avaiable for the requested range in other HTIME files. This is induced by changelog disable and enable which creates fresh HTIME index file. Cause and Analysis: Each HTIME index file represents the availability of continuous changelogs. If changelog is disabled and enabled, a new HTIME index file is created represents non availability of continuous changelogs. So as long as the requested start and end falls into single HTIME index file and not across, history API should succeed. But History API checks for the changelogs only in first HTIME index file and errors out if not available. Fix: Check in all HTIME index files for availability of continuous changelogs for requested change. fixes: bz#1622549 Change-Id: I80eeceb5afbd1b89f86a9dc4c320e161907d3559 Signed-off-by: Kotresh HR <khiremat@redhat.com>
Diffstat (limited to 'api/examples')
0 files changed, 0 insertions, 0 deletions