eth/tracers: fix unigram tracer's return value #22248
Merged
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.
Fixes #22208. The issue is that the tracer doesn't return a value (i.e. in js-land it returns
undefined
) if a tx was transfer-only, and one transfer tx in the block was enough to make the whole call fail.I'm not sure what's wrong with my go-bindata. I run
go generate eth/tracers/internal/tracers/tracers.go
but it changes the generated code by a bit.