This repository has been archived by the owner on Jun 11, 2024. It is now read-only.
Update lisk-codec to check int range during write #9010
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
Phanco
force-pushed
the
8968-range-check-for-writing-codec
branch
from
ead2caa to
aaca8df
Compare
Codecov Report
@@ Coverage Diff @@
## release/6.1.0 #9010 +/- ##
==============================================
Coverage 84.36% 84.37%
==============================================
Files 650 650
Lines 24017 24031 +14
Branches 3490 3494 +4
==============================================
+ Hits 20261 20275 +14
Misses 3756 3756
|
shuse2
suggested changes
Sep 19, 2023
...st/unit/modules/interoperability/mainchain/commands/terminate_sidechain_for_liveness.spec.ts
Show resolved
Hide resolved
shuse2
approved these changes
Sep 20, 2023
ishantiw
approved these changes
Sep 20, 2023
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.
What was the problem?
This PR resolves #8968
How was it solved?
How was it tested?