fix(logadmin): use consistent filter in paging example #8221
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Without supplying a
timestamp
in theListLogEntries.Filter
, the client by default sets one for the last twenty-four hours when theEntryIterator
is created. Since this example creates a newEntryIterator
on each request, a newtimestamp
of a slightly different twenty-four hour window is added. When theNext Page
button is pressed, it reuses theNextPageToken
from the previous call, but that was created for a different twenty-four hour windowFilter
. This creates a mismatch between the requestedFilter
and theFilter
used to create theNextPageToken
, resulting in an error.To address this, we create the filter in the main function before server start up. In this filter, we set a timestamp explicitly.
Note: I made this a
fix
commit because this is part of the GoDoc examples and we need this to appear as the latest release, otherwise no one will see it until another release comes along.Fixes #8186.