-
Notifications
You must be signed in to change notification settings - Fork 340
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
puller persists math.MaxUint64
interval on live syncing
#1623
Comments
This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 5 days. |
#2566 is related to this |
This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 5 days. |
@acud is this still relevant? |
This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 5 days. |
This issue was closed because it has been stalled for 5 days with no activity. |
Summary
While inspecting interval store persisted values from production, I found that the
math.MaxUint64
is persisted for some reason on certain intervals. This is a clear indication that we have an edge case inIntervalChunks
that is not handled correctly, since this interval should never be persisted.Steps to reproduce
No clue, yet.
But I assume that it should be visible if we look for the exact value when returning from the iterator.
Expected behavior
Interval should never be persisted.
Actual behavior
Interval persisted.
The text was updated successfully, but these errors were encountered: