Check if oldMachine is nil when updating process group #4180
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
dangra
approved these changes
Jan 21, 2025
|
I still don't love that I don't know why that is sometimes nil but this is a good defensive programming change anyway 🤷🏼 |
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.
Change Summary
Sometimes, the oldMachine field in the MachineTuple during deploys is nil and we don't check for this when loading from the healthCheckPassed sync map.
flyctl/internal/command/deploy/plan.go
Line 151 in 26a778e
What and Why:
This fixes a panic that users occasionally encounter during deploy
How:
Related to:
Documentation