-
Notifications
You must be signed in to change notification settings - Fork 367
fix: guard nil syncer dereference in statesync Reactor.Receive (backport #2883) #2931
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
Merged
rootulp
merged 2 commits into
v0.39.x-celestia
from
mergify/bp/v0.39.x-celestia/pr-2883
Apr 17, 2026
+64
−1
Merged
Changes from 1 commit
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
3 changes: 3 additions & 0 deletions
3
.changelog/unreleased/bug-fixes/statesync-nil-syncer-panic.md
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,3 @@ | ||
| - `[statesync]` Guard against nil syncer dereference in Reactor.Receive | ||
| when processing oversized SnapshotsResponse messages while no state sync | ||
| is in progress. | ||
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
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
Oops, something went wrong.
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.
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.
🟡 Changelog filename missing required issue/PR number prefix
Both
CONTRIBUTING.mdandCLAUDE.mdmandate that changelog entries follow the naming pattern{issue-or-pr-number}-{description}.md. The filestatesync-nil-syncer-panic.mdis missing the PR number prefix. All released changelog entries in the repo consistently use a number prefix (e.g.,2913-mempool-user-tx-latency-metric.md,3092-consensus-timeout-ticker-data-race.md). This PR is #2931, so the file should be named2931-statesync-nil-syncer-panic.md.Prompt for agents
Was this helpful? React with 👍 or 👎 to provide feedback.