Found by Cem Özer: Ignore older latest messages in attesting balance #1306
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.
Found by Cem Özer (@cemozerr): Ignore older latest messages in attesting balance sum, instead of assertion error.
Previously we asserted that the retrieved block was newer than the slot. But it may actually be older, if a latest message is older than the justified block (or later).
It is not breaking anything if there are no latest messages older than the justified epoch (not always the case). And I do not think that any clients are directly affected, as they are expected to not copy the inefficient spec implementation. It should be considered as a bug however.
Another option would be to check the lastest message slot, but we only track the epoch. Hence the decision to just return an empty hash in the query instead, which will always be different to the root being compared.