Skip to content
This repository was archived by the owner on May 31, 2025. It is now read-only.

ROS-O just the required commits#2388

Merged
sloretz merged 6 commits intonoetic-develfrom
sloretz_ros-o
May 9, 2025
Merged

ROS-O just the required commits#2388
sloretz merged 6 commits intonoetic-develfrom
sloretz_ros-o

Conversation

@sloretz
Copy link
Copy Markdown
Contributor

@sloretz sloretz commented May 9, 2025

#2297 got updated with commits that change the behavior of some packages. I'm opening a new PR set to a few commits back to avoid changing the ros-o:obese-devel branch

@jspricke FYI

@sloretz
Copy link
Copy Markdown
Contributor Author

sloretz commented May 9, 2025

LGTM. Verified desktop_full builds with this change.

@sloretz sloretz merged commit f25066d into noetic-devel May 9, 2025
2 checks passed
@sloretz sloretz deleted the sloretz_ros-o branch May 9, 2025 23:04
@jspricke
Copy link
Copy Markdown
Member

Awesome, thanks for your work!

@peci1
Copy link
Copy Markdown
Contributor

peci1 commented May 12, 2025

I see a new problem that might be connected to this PR: #2389 .

@jspricke
Copy link
Copy Markdown
Member

@peci1 I can't reproduce this on Debian (which includes this patches). Can you bisect where it is coming from instead of blaming some PR?

@peci1
Copy link
Copy Markdown
Contributor

peci1 commented May 12, 2025

Ah, right. I blamed this PR because it was the last one that touched the relevant files, but the error actually started appearing since #2277 (which makes sense, as it only started showing the errors).

I've debugged this locally and the culprit was in a few abruptly killed nodes that did not unregister from rosmaster. The /requestTopics XMLRPC request then tried to contact these dead sockets, so the error was actually correct.

Sorry for the noise.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants