This repository has been archived by the owner on Jun 11, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 15
Investigate lisk-core crash due to memory leak #1994
Merged
nagdahimanshu
merged 10 commits into
development
from
1993-investigate-lisk-core-crash-due-to-memory-leak
Dec 20, 2023
Merged
Investigate lisk-core crash due to memory leak #1994
nagdahimanshu
merged 10 commits into
development
from
1993-investigate-lisk-core-crash-due-to-memory-leak
Dec 20, 2023
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
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## development #1994 +/- ##
===============================================
- Coverage 68.14% 68.13% -0.02%
===============================================
Files 299 299
Lines 5324 5322 -2
Branches 975 973 -2
===============================================
- Hits 3628 3626 -2
Misses 1696 1696
|
priojeetpriyom
changed the title
1993 investigate lisk core crash due to memory leak
Investigate lisk-core crash due to memory leak
Dec 18, 2023
priojeetpriyom
force-pushed
the
1993-investigate-lisk-core-crash-due-to-memory-leak
branch
from
December 19, 2023 13:27
7a68a78
to
4582b39
Compare
vardan10
reviewed
Dec 19, 2023
Co-authored-by: Vardan Nadkarni <[email protected]>
nagdahimanshu
approved these changes
Dec 20, 2023
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM 👍
vardan10
approved these changes
Dec 20, 2023
nagdahimanshu
deleted the
1993-investigate-lisk-core-crash-due-to-memory-leak
branch
December 20, 2023 15:08
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 #1993
How was it solved?
pos_getExpectedSharedRewards
default value ofINVOKE_ALLOWED_METHODS
How was it tested?