fix: hex normalization in getTransactions #467
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
khanti42
requested review from
Akaryatrh and
stanleyyconsensys
and removed request for
a team
khanti42
force-pushed
the
fix/hex-normalization
branch
from
3e50a3b to
ca137ad
Compare
khanti42
force-pushed
the
fix/hex-normalization
branch
from
ca137ad to
076557c
Compare
stanleyyconsensys
previously approved these changes
Dec 18, 2024
stanleyyconsensys
approved these changes
Dec 18, 2024
|
|
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
QA session discovered an issue in the removal of transactions from State due to a misformatting of the transaction hash in State (does not comply with the 66 characters standard of Starknet). This PR solves this.