-
-
Notifications
You must be signed in to change notification settings - Fork 59
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: remove the assertion #136
Merged
vincenzopalazzo
merged 1 commit into
cloudhead:master
from
vincenzopalazzo:macros/sync_crash
Mar 1, 2024
Merged
fix: remove the assertion #136
vincenzopalazzo
merged 1 commit into
cloudhead:master
from
vincenzopalazzo:macros/sync_crash
Mar 1, 2024
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
vincenzopalazzo
force-pushed
the
macros/sync_crash
branch
from
April 7, 2023 11:35
d4a7788
to
805a4ae
Compare
vincenzopalazzo
force-pushed
the
macros/sync_crash
branch
2 times, most recently
from
June 25, 2023 11:42
3c546e6
to
dda1a47
Compare
This is done too! As we discuss I moved to log information on some of the asserts. The more strange one I moved to warnings |
vincenzopalazzo
force-pushed
the
macros/sync_crash
branch
from
December 31, 2023 13:20
dda1a47
to
4394ac2
Compare
I rebased this and we should merge it otherwise nakamoto is not usable in debug mode, recently it is crashing a lot |
This commit removes the debug assert since it occurs a few times. Therefore, the debug assert is replaced with a warning log line, allowing us to track the frequency of this occurrence. Signed-off-by: Vincenzo Palazzo <[email protected]>
vincenzopalazzo
force-pushed
the
macros/sync_crash
branch
from
December 31, 2023 13:22
4394ac2
to
08203fd
Compare
LGTM! |
cygnet3
added a commit
to cygnet3/sp-client
that referenced
this pull request
Feb 21, 2024
The forked dependency currently also includes the commit from this PR: cloudhead/nakamoto#136 This is needed to avoid crashing on an assertion that seems to be fairly common.
cygnet3
added a commit
to cygnet3/sp-client
that referenced
this pull request
Feb 21, 2024
The forked dependency currently also includes the commit from this PR: cloudhead/nakamoto#136 This is needed to avoid crashing on an assertion that seems to be fairly common.
cygnet3
added a commit
to cygnet3/sp-client
that referenced
this pull request
Feb 21, 2024
The forked dependency currently also includes the commit from this PR: cloudhead/nakamoto#136 This is needed to avoid crashing on an assertion that seems to be fairly common.
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.
It is not clear to me when this happens, but from how the sync function is written there any reason to assert and fails.
Also, while start a new negotiation with a new peer, looks like pretty common get a peer with a different height that maybe is the wrong one?
The crash that I see on my system is
Fixes #137