EVM-677: Fix log index issue on eth_getTransactionReceipt
#1576
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.
Description
eth_getTransactionReceipt
did not return correct indexes of logs. For example, if we had a block with 2 transactions with 2 logs each, and if we want a receipt from the second transaction, the function would return log indexes 0, 1, instead of 2, 3, since there is a transaction in the block that had logs before the desired transaction.This PR fixes the issue and adds new UT.
This is continuation of work from PR 1533.
Changes include
Checklist
Testing