ros2 / ros2/ros2cli

`ros2 node list`, `ros2 service list` and `ros2 param list` randomly display information on Windows

Open
#876 0 comments 0 reactions 1 assignee View on GitHub

@mjcarroll is already working on this.

Since Jan 25, 2024.

Dominant language
Python
Stars
262
Forks
228
Avg merge
23h 15m
Merged PRs (30d)
12

Description

Bug report

Required Info:

  • Operating System:
    • Windows 11
  • Installation type:
    • binary, installed from aka.ms/ros (I could not get the normal version working) with:
choco source add -n=ros-win -s="https://aka.ms/ros/public" --priority=1
choco upgrade ros-humble-desktop -y --execution-timeout=0 --pre

And my Microsoft.Powershell_profile.ps1 contains at the end:

$ROS_DOMAIN_ID=0
C:\opt\ros\humble\x64\setup.ps1
  • Version or commit hash:
    • Humble Hawksbill
  • DDS implementation:
    • Didn't touch that, I think the default is Fast DDS ?
  • Client library (if applicable):
    • ?
  • Python version in path (before ros2's setup):
    • 3.12.1
Steps to reproduce issue

Run

ros2 run turtlesim turtlesim_node

then

ros2 node list

a bunch of times, and

ros2 service list

a bunch of times.

Expected behavior

Command always containing the list of nodes / services

Actual behavior

image
The /turtlesim node was found 10 out of 16 times in my test

image
The services where found 8 out of 16 times in my test

Edit: I get the same bug with ros2 param list

When trying to get more information about a node or service that doesn't exist, for example ros2 service type /clear, the command just exits with exit code 1.

Additional information

When using rqt 'Plugins' > 'Introspection' > 'Node graph', nodes always display, and when using the 'Service Caller', services always show up.

A similar issue is #582 but this one seems to be fixed

For the fancy PowerShell displaying, I use oh-my-posh

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.