feat(event): skip log warning for certain scenario #4974
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
tomatoishealthy
force-pushed
the
feature/event-log-optimize
branch
from
92a053b to
c62ab67
Compare
tomatoishealthy
changed the title
tomatoishealthy
force-pushed
the
feature/event-log-optimize
branch
from
c62ab67 to
6b85322
Compare
tomatoishealthy
force-pushed
the
feature/event-log-optimize
branch
from
6b85322 to
66c80e9
Compare
tomatoishealthy
force-pushed
the
feature/event-log-optimize
branch
from
66c80e9 to
057f3f0
Compare
halibobo1205
approved these changes
Feb 13, 2023
waynercheung
approved these changes
Feb 13, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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 does this PR do?
Skip log warning when solidity block number is 0.
Why are these changes required?
This PR has been tested by:
Follow up
Extra details