NEAR Indexer Framework 0.9.1 Release notes (hot-fix) #4318
khorolets
started this conversation in
Node Public Interfaces
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
This version is a hotfix on top of nearcore release 1.19.0
See CHANGELOG
TL;DR
You need to change nearcore dependency commit hash and rebuild your indexer. No changes in the logic are required. No issues with rebuilding are expected.
What had happened?
In 0.9.0 we totally missed the concept of delayed local receipts and that might cause your indexer to panic and stop working.
Local receipt is a kind of receipt where sender equals the receiver. Such receipt isn't stored in internal database. However execution outcome for such receipt may appear in later block (that's why it is delayed local receipt). Indexer is unable to get the receipt for execution outcome from internal database by it's ID if the receipt we're looking for is local one.
The problem was actually caused by recent change where we introduced
IndexerExecutionOutcomeWithOptionalReceipt
and changedreceipt
field inIndexerExecutionOutcomeWithReceipt
mandatory (as I've mentioned we missed the concept of delayed local receipt).To avoid introducing breaking changes we made NEAR Indexer Framework able to "travel in time" and look for local receipt in previous blocks. It will loop over past blocks one by one looking for the receipt to attach it to
IndexerExecutionOutcomeWithReceipt
. If it is doesn't find the receipt in previous 1000 blocks indexer will panic.The described behaviour will be optimized, here's in the #4317 stay tuned.
Sorry for inconveniences.
Beta Was this translation helpful? Give feedback.
All reactions