8000 Accessing numerical parameter causes exception · Issue #337 · ros2/launch_ros · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content
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

Accessing numerical parameter causes exception #337

Closed
wep21 opened this issue Dec 3, 2022 · 0 comments · Fixed by #338
Closed

Accessing numerical parameter causes exception #337

wep21 opened this issue Dec 3, 2022 · 0 comments · Fixed by #338

Comments

@wep21
Copy link
Contributor
wep21 commented Dec 3, 2022

Bug report

Required Info:

  • Operating System:
    • Ubuntu 22.04
  • Installation type:
    • binaries
  • Version or commit hash:
    • ros-humble-launch-ros:
      Installed: 0.19.3-1jammy.20221108.174822
      Candidate: 0.19.3-1jammy.20221108.174822
      Version table:
      *** 0.19.3-1jammy.20221108.174822 500
      500 http://packages.ros.org/ros2/ubuntu jammy/main amd64 Packages
      100 /var/lib/dpkg/status
  • DDS implementation:
    • cyclonedd
  • Client library (if applicable):

Steps to reproduce issue

<launch>
  <set_parameter name="foo" value="1.0" />
  <log message="$(param foo)" />
</launch>

Expected behavior

[INFO] [launch]: All log files can be found below /home/daisuke/.ros/log/2022-12-03-21-47-40-384872-npc2007011-28977
[INFO] [launch]: Default logging verbosity is set to INFO
[INFO] [launch.user]: 1.0

Actual behavior

❯ ros2 launch test.launch.xml
[INFO] [launch]: All log files can be found below /home/daisuke/.ros/log/2022-12-03-21-48-18-159550-npc2007011-29116
[INFO] [launch]: Default logging verbosity is set to INFO
[ERROR] [launch]: Caught exception in launch (see debug for traceback): sequence item 0: expected str instance, float found

Additional information


Feature request

Feature description

Implementation considerations

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 a pull request may close this issue.

1 participant
0