Fix multi-instance publishing of satellite_info topic #23567
Merged
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.
Solved Problem
When debugging some GNSS issues I found that only the main instance of satellite_info topic was logged. This is annoying when you need to find out why one GNSS is degraded compared to the other one.
Solution
_is_gps_main_advertised.load()
the same way as sensor_gps is publishedChangelog Entry
For release notes:
Test coverage
There are two gps instances as confirmed by sensor_gps, but only one satellite_info
Now there are two instances of satellite_info that are logged correctly (
satellite_info.00
andsatellite_info.01
), but also still a "zombie"satellite_info
that contains one datapoint from what I can see...