feat(opt): opt format name and gRPC - #3
Open
waynercheung wants to merge 4 commits into
Open
Conversation
Preserve Fastjson-compatible root-value parsing and add focused regression coverage. Use the default hexadecimal representation for transaction contract names.
…mat-name fix: harden gRPC HTTP/2 stream limits
waynercheung
changed the title
waynercheung
force-pushed
the
feat/opt_format_name
branch
3 times, most recently
from
July 31, 2026 07:54
ded2fa5 to
71c7c7e
Compare
waynercheung
force-pushed
the
feat/opt_format_name
branch
from
July 31, 2026 08:55
71c7c7e to
a0a53d4
Compare
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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?
Why are these changes required?
This PR has been tested by:
Follow up
Extra details