-
Notifications
You must be signed in to change notification settings - Fork 17
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
Data is lost in block 22633808 #47
Comments
@telezhnaya could you check please, I've made near-lake-indexer to run against that block again. |
@khorolets ideally, we should have looked at what was the state of those files before rewriting and why near-lake-framework-rs passed incomplete StreamMessage down the line 🧐 |
@khorolets we still have this problem |
OK, I've checked. I want to pass it on to you @telezhnaya I've found the May I ask you to find out why the heck the 22635169 `StreamerMessage`
|
Are you sure it's for me? We just listen to the blockchain, we don't create this data from nowhere |
@telezhnaya My main concern is why we have stored that piece of data in indexer for explorer db the way we have. I am going to check the archival indexer data to narrow down the questions who's mistake is that and will update you. |
My checks on the archival node with Indexer Framework prove that Since the data reflected by Lake Indexer is correct I am closing this issue and I am going to open an issue on Indexer for Explorer project to figure out the reason the record in the database is incorrect. |
I feel it's still an issue for this project. Inside lake, we have json with block 22633808, where one field explicitly says "hey, we have the other useful data in the other field", and the second field is empty |
I disagree. Lake indexer doesn't say we have execution outcome for this receipt in that block. Have a look at my comment with attached logs from Indexer Framework. The block you refer to just doesn't contain |
At json about block 22633808, we see this
The fee was taken. As I understand the blockchain logic, it means that the receipt should be executed in the same block. |
Wow, it looks like it's not the fee. |
For future me: select * from account_changes
where account_changes.affected_account_id = 'aspaceodyssey2001.near' and
account_changes.changed_in_block_timestamp > 1604411776828600726
and account_changes.changed_in_block_timestamp <= 1605411776828600726; plus some calc |
@khorolets @telezhnaya This was an instance of duplicate transaction execution. Blocks
|
Here are the transaction and the receipt you're referring to, I believe: Thank you @frol for digging into it. Your input is very useful! We're trying to understand the data flow behind these actions. Talking about blocks
But At the same time, Indexer for Explorer says the So my main assumption is that we might have introduced some changes to the Indexer Framework that we are no longer able to collect the What do you think? |
This is an unpleasant mystery. I have no better guesses, but I don't see how that could have happened. |
While investigating https://github.com/telezhnaya/indexer_balances/issues/1, I've found the issue
We have the receipt in this block, but we don't have execution_outcome
Please check why
receipt_execution_outcomes
is empty for block 22633808The text was updated successfully, but these errors were encountered: