Skip to content

Navigation Menu

Explore
By company size
By use case
By industry
View all solutions
Topics
- AI
- DevOps
- Security
- Software Development
- View all
Explore
- GitHub Sponsors
  Fund open source developers
- The ReadME Project
  GitHub community articles
Repositories
- Enterprise platform
  AI-powered developer platform
Available add-ons
Pricing

Search code, repositories, users, issues, pull requests...

Search

Clear

Search syntax tips

Provide feedback

We read every piece of feedback, and take your input very seriously.

Include my email address so I can be contacted

Saved searches

Use saved searches to filter your results more quickly

Name

Query

To see all available qualifiers, see our documentation.

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session.

Dismiss alert

ros2 / rclpy Public

Notifications You must be signed in to change notification settings
Fork 233
Star 316

Code
Issues 106
Pull requests 22
Actions
Security
Insights

Additional navigation options

Code
Issues
Pull requests
Actions
Security
Insights

Raise custom error when node name is not found#413

Merged

ivanpauno merged 5 commits intomasterros2/rclpy:masterfrom ivanpauno/add-error-for-non-existent-noderos2/rclpy:ivanpauno/add-error-for-non-existent-nodeCopy head branch name to clipboard

Sep 17, 2019

+43-6

Conversation Commits5 (5)Checks Files changed

Commits

Commits on Sep 16, 2019

Raise custom exception when rclpy_get_*_names_and_types_by_node doesn't find a node name
ivanpauno
committed
Delete commented line
ivanpauno
committed
Move new exception to node.py
ivanpauno
committed
Use CamelCase instead of snake_case in exception names
ivanpauno
committed
Delete old code
ivanpauno
committed

Footer

© 2025 GitHub, Inc.

Footer navigation

Terms
Privacy
Security
Status
Docs
Contact

You can’t perform that action at this time.