-
Notifications
You must be signed in to change notification settings - Fork 43
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
Missing sequences #69
Comments
Ah then maybe backfiller should be checking if there are 1-1 match between distinct leaf ids & right_most_path length of the tree |
So here's my example tree for this issue:
So missing sequences 3,8,11,26,68,97,115 in the DB. Here are the sequence numbers, node idx, transactions:
|
However, in all these cases it looks like in |
I see, this actually make sense since
So these sequence numbers were ingested correctly but then just overridden.. Now I'm not clear quite still how the metaplex indexer handles the scenario where the Transfer transaction would be indexed before the Mint one. |
Believe this has been solved. |
Since there's no way to reindex missing sequence number if a new sequence number has been ingested for the same node_idx, this means we end up with missing sequence numbers in the DB any time a future transaction is indexed before a previous one has been indexed.
So far we haven't observed this creating practical issues but I am not sure if it shouldn't mean problem if say, a transfer instruction is processed before the corresponding mint instruction. In this case the ownership change should fail since it calles
update_asset
and this update_asset call won't work because the asset is not present in the DB?The text was updated successfully, but these errors were encountered: