Skip to content

Fix issue where XRCE_DDS Bridge did not respect environment variables #25231

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

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

sansha
Copy link

@sansha sansha commented Jul 16, 2025

Solved Problem

Fixes #25188 (detailed description in that issue)

Solution

Hi, this is the PR fixing #25188 by removing the -h 127.0.0.1 flag in the launch command for the client.
This fix works for me, not sure if other setups are affected.

Let me know your thoughts!

Changelog Entry

For release notes:

Feature/Bugfix Fix bug where UXRCE_DDS_AG_IP was not read when launching the xrce client in SITL.

Alternatives

In the first commit I load the env variable explicitly but changed this to just remove the flag since I cannot test this right now. But this of course would also be an option

Test coverage

Context

Related links, screenshot before/after, video

Copy link
Member

@beniaminopozzan beniaminopozzan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

thanks @sansha , could you set the default value for the IP address in simulation to 127.0.0.1 to maintain back-compatibility?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Bug] XRCE_DDS Bridge does not work in SITL across docker containers because PX4_PARAM_UXRCE_DDS_AG_IP is not respected
2 participants