-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Not unique logIndex
#12549
Comments
Response from my calibnet node:[
{
"address": "0x493cd7e48854582eb9aa3a303c06984d23f5a30e",
"data": "0x000000000000000000000000000000000000000000000002fa12c7332fe0932d",
"topics": [
"0xddf252ad1be2c89b69c2b068fc378daa952ba7f163c4a11628f55a4df523b3ef",
"0x0000000000000000000000000000000000000000000000000000000000000000",
"0x000000000000000000000000f0e7d903ef892ac5fe7020f15c29ec1f6a10e9f3"
],
"removed": false,
"logIndex": "0x1",
"transactionIndex": "0x1",
"transactionHash": "0x4a2c9d4aa7bf56ea34e9e5e751beb577c45c93d38ba825af2b95e34ef5635350",
"blockHash": "0xbf3c2cbfb12cb7238741fa15b311a98e1158fcb19766c56547fb55ef77838407",
"blockNumber": "0x1b18b4"
},
{
"address": "0x493cd7e48854582eb9aa3a303c06984d23f5a30e",
"data": "0x000000000000000000000000000000000000000000000002fa12c7332fe0932d",
"topics": [
"0x9d228d69b5fdb8d273a2336f8fb8612d039631024ea9bf09c424a9503aa078f0",
"0x000000000000000000000000f0e7d903ef892ac5fe7020f15c29ec1f6a10e9f3",
"0x00000000000000000000000051e1f72b655528de2d4d88e70bd53774db8d0b0c"
],
"removed": false,
"logIndex": "0x2",
"transactionIndex": "0x1",
"transactionHash": "0x4a2c9d4aa7bf56ea34e9e5e751beb577c45c93d38ba825af2b95e34ef5635350",
"blockHash": "0xbf3c2cbfb12cb7238741fa15b311a98e1158fcb19766c56547fb55ef77838407",
"blockNumber": "0x1b18b4"
},
{
"address": "0x51e1f72b655528de2d4d88e70bd53774db8d0b0c",
"data": "0x000000000000000000000000000000000000000000000002fb474098f67c0000000000000000000000000000000000000000000000000002fa12c7332fe0932d",
"topics": [
"0x90890809c654f11d6e72a28fa60149770a0d11ec6c92319d6ceb2bb0a4ea1a15",
"0x000000000000000000000000f0e7d903ef892ac5fe7020f15c29ec1f6a10e9f3"
],
"removed": false,
"logIndex": "0x3",
"transactionIndex": "0x1",
"transactionHash": "0x4a2c9d4aa7bf56ea34e9e5e751beb577c45c93d38ba825af2b95e34ef5635350",
"blockHash": "0xbf3c2cbfb12cb7238741fa15b311a98e1158fcb19766c56547fb55ef77838407",
"blockNumber": "0x1b18b4"
}
] I can't see how we could end up with duplicate I think what we're seeing here is pre-v1.27.1 behaviour being locked into the index, and because you're reaching back that far you're encountering the original bug that was filed for this @ #11630. Is this a problem for you @nikitosing? We'd be able to come up with some suggestions for how you might correct this, but it'd either be some gnarly SQL to run on the database, or a delete and backfill of the impacted epochs, which is only going to work if you have the full historical state to rebuild the events from. |
@rvagg Yes, I think that's the case.
it's ok, we have the full historical state |
@rvagg Could you please share your suggestions about workaround for the issue? |
@nikitosing can you run this, so we can see what we're dealing with? Given the path to your lotus repo dir, we want to run
And let me know what the number it comes back with is and we'll think about it from there. The problem is, there was a migration in #11952 that was supposed to properly order all of these so you didn't have duplicates, so I'm actually not sure how you can end up with it in a bad state like this: https://github.com/filecoin-project/lotus/pull/11952/files#diff-fe5e47a357d5465c3a2b1002977a53ad7c0990f76da22137417723577b87b19eR382 |
@rvagg result is |
@nikitosing that's a big number. Would you mind compiling |
Checklist
Latest release
, the most recent RC(release canadiate) for the upcoming release or the dev branch(master), or have an issue updating to any of these.Lotus component
Lotus Version
Repro Steps
{"jsonrpc":"2.0","id":2,"method":"eth_getTransactionReceipt","params":["0x4A2C9D4AA7BF56EA34E9E5E751BEB577C45C93D38BA825AF2B95E34EF5635350"]}
Describe the Bug
Expected behavior
logIndex should be unique per block and per transaction
Logging Information
The text was updated successfully, but these errors were encountered: