Skip to content

Fix GraspObjectNode initializaton order for ROS 2 humble#235

Open
hello-jkoubi wants to merge 1 commit into
humblefrom
fix/grasp-object-initialization-order
Open

Fix GraspObjectNode initializaton order for ROS 2 humble#235
hello-jkoubi wants to merge 1 commit into
humblefrom
fix/grasp-object-initialization-order

Conversation

@hello-jkoubi

@hello-jkoubi hello-jkoubi commented Jun 16, 2026

Copy link
Copy Markdown
Contributor

Summary

Fix an initialization-order issue in grasp_object on ROS 2 Humble.

MoveBase was being constructed before the underlying ROS node was fully initialized. Since MoveBase declares ROS parameters during initialization, ros2 run stretch_demos grasp_object resulted in:

AttributeError: 'GraspObjectNode' object has no attribute '_parameter_overrides'

This change delays MoveBase initialization until after HelloNode.main() completes, ensuring the node is fully initialized before parameters are declared.

Testing Notes

grasp_object.py depends on stretch_funmap Python packages through the virtual environment workflow.

To test this PR, first apply the companion venv-wrapper PR and re-wrap the stretch_demos executables:

REx_amend_venv_execs.py stretch_demos --venv-package stretch_funmap --force

Then verify that the node starts successfully:

ros2 run stretch_demos grasp_object

Before this fix, the command failed during startup with:

AttributeError: 'GraspObjectNode' object has no attribute '_parameter_overrides'

After this change, grasp_object should initialize successfully.

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.

1 participant