Check for null value on TRACE_FORMATTERS.transactionHash #2965
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.
What was wrong?
We are running a Gnosis Safe instance for Ethereum Classic chains.
The indexer of Gnosis Safe, uses
trace_block
to fetch some info.This implementation works fine on Ethereum network now that is on PoS. The
trace_block
tracer returns only the traces for the block transactions.On the other hand, on Ethereum Classic, we include two more objects at the end of the array, which are the block and uncle rewards. Those two entries don't have a
transactionHash
, and it's being set tonull
.For this reason we trigger the following exception:
How was it fixed?
By checking if trace
transactionHash
is null.Todo:
Cute Animal Picture