This repository has been archived by the owner on Feb 6, 2025. It is now read-only.
fix: support of trace API #216
Merged
Conversation
This file contains 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
pythonberg1997
force-pushed
the
develop
branch
from
875ac0e to
fa76ff9
Compare
pythonberg1997
force-pushed
the
develop
branch
from
edc89ef to
425a6f2
Compare
unclezoro
approved these changes
Jan 13, 2025
j75689
approved these changes
Jan 16, 2025
yutianwu
approved these changes
Jan 16, 2025
This was referenced Jan 20, 2025
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Description
This pr is to fix some issue of trace API
Rationale
The trace API was not working previously due to certain BSC parlia consensus behaviors
Example
add an example CLI or API response...
Changes
Notable changes:
Potential Impacts