fix(dashmate): failed to read docker data on update - #1903
Merged
Conversation
shumkov
approved these changes
Jun 23, 2024
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
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.
Issue being fixed or feature implemented
Update command seems broken, might be after #1685 or docker might have updated their format again.
If you issue dashmate update command, we can see that all services marked as error:
And if we add DEBUG=1 to the environment, there is a continuous repeat of the
Failed to read docker json data, status not founderror message.The reason is that latest check on status in the updateNodeFactory is excessive, when no message starting with
Status:is found in the stream data event. Because the status are sent in chunks, it is expected that status may be null.
What was done?
Removed check when status not found from stream data event.
How Has This Been Tested?
Locally. Now error is gone, and everything updates correctly:
If you intentionally set invalid dashd version in the config, then it shows error as expected:
Breaking Changes
Checklist:
For repository code-owners and collaborators only