-
Notifications
You must be signed in to change notification settings - Fork 881
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
[18.09 backport] Fix possible nil pointer exception #2327
[18.09 backport] Fix possible nil pointer exception #2327
Conversation
Same as other back port.
|
can you also add this commit? #2320 that fixes the gosimple |
Ah, need to backport #2320 to the release branches |
LOL, yes, so that ^^ haha |
ahah I was 3s faster :D |
Signed-off-by: Flavio Crisciani <[email protected]> (cherry picked from commit fd6be31) Signed-off-by: Sebastiaan van Stijn <[email protected]>
I opened separate pull requests for them (for all the release branches) |
@thaJeztah the problem is that also this PR fix a gosimple issue. so the other PR will still fail |
Ah, gotcha; probably need to take just that bit from the PR to backport to 17.06 😕 |
It is possible that the node is not yet present in the node list map. In this case just print a warning and return. The next iteration would be fine Signed-off-by: Flavio Crisciani <[email protected]> (cherry picked from commit 1954e1c) Signed-off-by: Sebastiaan van Stijn <[email protected]>
160db4f
to
d20ece4
Compare
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, failure is unrelated
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
backport of #2325 for 18.09
relates to moby/moby#38618
cherry-pick was clean; no conflicts
It is possible that the node is not yet present in
the node list map. In this case just print a warning
and return. The next iteration would be fine