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: Fixing syntax within EventScanner's scan_chunk method #2487

Closed

Conversation

0xRadiant
Copy link

@0xRadiant 0xRadiant commented May 26, 2022

What was wrong?

Related to Issue #2486

How was it fixed?

Assigning the event, block number, and count to their own variables and pass them in to the logger.debug message.

@@ -991,8 +991,12 @@ The script can be run with: ``python ./eventscanner.py <your JSON-RPC API URL>``
# Get UTC time when this event happened (block mined timestamp)
# from our in-memory cache
block_when = get_block_when(block_number)

logger.debug(f"Processing event {evt["event"]}, block: {evt["blockNumber"]} count: {evt["blockNumber"]}")
Copy link
Author

Choose a reason for hiding this comment

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

I also noticed that count and block both refer to evt["blockNumber"]. I'm not yet sure if this was intentional. If this is not intended, we can address this in the same pull request.

Copy link
Collaborator

Choose a reason for hiding this comment

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

I don't think that was intentional, please feel free to update! Thanks!

@kclowes
Copy link
Collaborator

kclowes commented Jun 8, 2022

This got fixed in #2504. Thanks for the PR @0xRadiant!

@kclowes kclowes closed this Jun 8, 2022
@0xRadiant 0xRadiant deleted the examples-eventscanner-fix branch June 14, 2022 00:58
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