-
Notifications
You must be signed in to change notification settings - Fork 225
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
Create custom exceptions in _rclpy.c #31
Comments
@mikaelarguedas I would like to like to contribute |
@suab321321 I haven't been involved in this project for a long time so can't provide feedback about the status / relevance of this ticket with respect to the current code base. |
It looks like we have a few custom exceptions defined already: rclpy/rclpy/src/rclpy/_rclpy.c Lines 43 to 45 in d375c84
But a quick search yields several places in _rclpy.c that raise @suab321321 If you'd like to contribute to this ticket, I think a good first step would be to replace instances of RuntimeError with a new RCLError whenever there's a failed call to the rcl layer. rclpy/rclpy/src/rclpy/_rclpy.c Lines 5088 to 5099 in d375c84
|
@jacobperron okay sir I will proceed with this |
@jacobperron sir I have to make RCLError first right? |
Correct. You can declare and initialize it in the two places of the code I referenced (#31 (comment)). |
#478 here @jacobperron sir |
For now every failure in rclpy raises a
RuntimeError
, we should create custom errors for different failure scenarios and avoid the tests of just catching random RuntimeErrors.The text was updated successfully, but these errors were encountered: