tree 0f9f34c9e802e49952b326822d7bccf3b324b0b6
parent efde4ec92bdad203f611c4f369877a770f315ba5
author Jason M. Bills <jason.m.bills@intel.com> 1656019144 -0700
committer Ed Tanous <ed@tanous.net> 1656374826 +0000

Update handling of skipped log entries

We now skip log entries where the MessageId is not in the Message
Registry. However, since a blank entry is added to the array before the
MessageId is checked, it was leaving an empty {} in that location and
incrementing the Members@odata.count.

This change moves the MessageId check to before the entry count is
incremented to fix the Members@odata.count and moves the push_back()
into the array to the end, so an entry is only added if it's valid.

Tested:
Added three entries to the log as follows: good, bad, good.
The entries array showed only the two good entries with
Members@odata.count=2.
Using top=2, still showed only the two good entries with
Members@odata.count=2.
Skip did not work but appears to already be broken, so it was not
impacted by this change.
Confirmed that getting a single good entry still works.

Change-Id: I08ffc56af14004e2221acdb4a091bbfeb9c21c70
Signed-off-by: Jason M. Bills <jason.m.bills@intel.com>