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 process_log
for HexStr
inputs
#3293
Conversation
2da8c5b
to
b8a0691
Compare
b8a0691
to
690a03e
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just one nit which adds a bit of unnecessary overhead, wrapping with @curry
where we don't need to. Looks good otherwise 👍🏼
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Agree with the @curry
nit, otherwise lgtm!
`HexStr` values now converted to bytes for processing
690a03e
to
722df5c
Compare
71e9467
to
e67db77
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm!
What was wrong?
Related to Issue #3286
Realized the topics and data values had not been explicitly converted to bytes. The initial fix I made was to convert the log topics to a
HexStr
but since bytes are needed later on, it made sense to just ensure everything is coerced to bytes before handling them.How was it fixed?
Explicit type coercion of entry
topics
anddata
values.Todo:
Cute Animal Picture