Fixes to correctly build and run a docker container with the GOOSE node type#1000
Open
Fixes to correctly build and run a docker container with the GOOSE node type#1000
Conversation
added 2 commits
February 6, 2026 16:59
…isher Signed-off-by: Calvin Katt <calvin.katt@rwth-aachen.de>
Signed-off-by: Calvin Katt <calvin.katt@rwth-aachen.de>
…xists Signed-off-by: Calvin Katt <calvin.katt@rwth-aachen.de>
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
1 participant
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.
Adds nullptr checks in the iec61850_goose node type to prevent a segmentation fault. When the process has insufficient permissions to open a raw socket, the returned goose publisher is a nullptr.
Sets pip to a fixed version (25.3) since the container build fails with the latest pip version (26.0.1)
Create publishers if only output section exists.