Skip to content
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

Fix LogsBloom formatter error #1445

Merged
merged 1 commit into from
Sep 19, 2019

Conversation

enjeyw
Copy link
Contributor

@enjeyw enjeyw commented Sep 5, 2019

What was wrong?

When getBlock(block_identifier='pending') is called, the pending block will return logsBloom = null. The current block formatter attempts to convert the null value to HexBytes and fail.

How was it fixed?

The LogsBloom HexBytes formatter is only applied when logsBloom is not null.

Todo:

Cute Animal Picture

lilly

@kclowes
Copy link
Collaborator

kclowes commented Sep 5, 2019

That parity test is flaky, not something you did. Do you mind adding a test for this functionality? Thanks!

Copy link
Collaborator

@kclowes kclowes left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looking into this, I don't think it's testable with the versions of geth and parity that we use for our integration testing. It looks like this problem was fixed in geth 1.5 (see here), and parity doesn't have a pending option as of 1.1.11 (see here). That being said, this looks good to me! Thanks @enjeyw!

@kclowes kclowes force-pushed the fix_logsbloom_format_error branch from 08e1229 to 4fb9319 Compare September 19, 2019 17:35
@kclowes kclowes merged commit 6f9889a into ethereum:master Sep 19, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants