executors behind warning
Open
Nobody has claimed this yet.
bug
- Dominant language
- Python
- Stars
- 589
- Forks
- 76
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 3
Description
Describe the bug
No matter which executor MultiThreadedExecutor or SingleThreadedExecutor is used in manipualtion demo, following warning appears:
MultiThreadedExecutor is 1.47 seconds behind. If you see this message frequently, consider switching to SingleThreadedExecutor.
It does not produce any bugs that I m aware of, but can impact performance
To Reproduce
Steps to reproduce the behavior:
- Run manipulation demo
- Check out logs
Platform
- OS: Ubuntu 24.04
- ROS 2 Jazzy
Version
414c328602f7d357eac6a8229d235555d619b0e4
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the warning while running the manipulation demo on Ubuntu 24.04 with ROS 2 Jazzy, and compare the logs for both executor types. Trace the manipulation demo's executor setup and warning source; done means determining the cause and either removing the unintended delay or documenting why the warning is expected.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- performance, robotics
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100