-
Notifications
You must be signed in to change notification settings - Fork 15
Fix node registration, filtergateway, and scenario processing bugs #400
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
base: main
Are you sure you want to change the base?
Conversation
- Modified find_node_by_simple_key() to skip invalid IPs (0.0.0.0, 127.0.0.1, empty) - Iterates through all nodes to find first valid IP instead of just returning first found - Added new find_node_by_target_ip() function for specific IP lookups - Prevents node registration from returning wrong/unusable IP addresses
…-pullpiri#389] - Check if scenario has valid conditions before subscribing to DDS topic - Skip subscription when topic name is empty to prevent dummy data - Added logging for skipped subscriptions for debugging - Fixes issue where empty conditions caused unwanted DDS data publishing
…i#386] - Changed apply() to return Vec<String> instead of single String - Collects all scenarios from multi-document YAML, not just the last one - Updated apply_artifact() to send all scenarios to FilterGateway - Updated tests to handle new return type - Fixes issue where only last scenario in YAML file was being processed
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.
I deeply appreciate your contribution.
This section inserts a random node when the package fails to find a node to run on. As a result, the code shouldn't be executed, and it would be better to fundamentally change the part before this point.
| || ip_address == "127.0.0.1" | ||
| { | ||
| println!("Skipping invalid IP: {}", ip_address); | ||
| continue; |
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.
Sometimes, IP can be 127.0.0.1 or 0.0.0.0.
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.
very nice bug fix
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.
Good.
However, no decision has yet been made on whether to allow multi-scenarios.
|
@ANAVHEOBA Thanks for the contribution!! Unfortunately, you need Eclipse FDN for PR to be merged. So, you need to join Eclipse foundation and submit some materials for getting ECA. If you are still considering the contribution, please get Eclipse FDN/ECA. Thanks. |
Summary
This PR addresses three open issues related to node registration, DDS subscription handling, and scenario processing.
Changes
#391 - Node registration wrong IP
find_node_by_simple_key()to filter out invalid IPs (0.0.0.0, 127.0.0.1, empty)#389 - Filtergateway condition bug
#386 - Scenario processing only last scenario
apply()to return all scenarios from YAML, not just the last oneTest Plan