You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The following pages have either non-increasing (duplicate) commit timestamps from one page to the next or decreasing. Catalog leaves are expecting to be monotonically increasing and this is not the case on some very old leaves.
For the negative delta case, there appears to be a leaf that got written at the end of one page and at the beginning of the next. The leaf URL is different.
For the first 0 case, a batch of 2 items was written at the end of one page and again at the beginning of the next page (with an additional item upon retry)
Similar with the second 0 case:
This also means some leaf URLs appear in multiple pages, which is not expected:
Impact
It bothers me. A fix would be nice
Describe the bug
The following pages have either non-increasing (duplicate) commit timestamps from one page to the next or decreasing. Catalog leaves are expecting to be monotonically increasing and this is not the case on some very old leaves.
For the negative delta case, there appears to be a leaf that got written at the end of one page and at the beginning of the next. The leaf URL is different.
For the first 0 case, a batch of 2 items was written at the end of one page and again at the beginning of the next page (with an additional item upon retry)
Similar with the second 0 case:
This also means some leaf URLs appear in multiple pages, which is not expected:
Repro Steps
Run the queries above against NuGet Insights.
Expected Behavior
Commit timestamps should be monotonically increasing.
A catalog leaf URLs should only appear in a single page.
The commit ID and commit timestamp on the page leaf item should match the full leaf document. This is not the case for the duplicate leaf URLs.
Screenshots
No response
Additional Context and logs
No response
The text was updated successfully, but these errors were encountered: