Do not call node.GetChains()
if node is nil
#1588
Merged
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.
In
NewSessionNodes
, the variablenode
can benil
if the node is unstaked betweensessionCtx
andctx
. In such a case,node.GetChains()
causes a panic. This patch makes sure we don't call it if thenode
isnil
.This is a regression from #1582.
Description
Summary generated by Reviewpad on 21 Dec 23 10:23 UTC
This pull request fixes a regression introduced in #1582. The patch ensures that the function
node.GetChains()
is not called if thenode
isnil
, preventing a panic in theNewSessionNodes
function.