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
The DynamicReconfigure Server class always return success upon SetConfigCallback service call, regardless of whether the new config was successfully derived from the service request.
If, by accident, you call the service with a wrong configuration, the __fromMesage__ function will fail since it won't be able to update the new_config, acording to server.h L219.
The __fromMesage__ function actually returns the result of the process, so I propose using the result to populate the service response correctly so the service caller can actually identify if the call failed.
Describe the bug
Branch: noetic-devel
The DynamicReconfigure Server class always return success upon
SetConfigCallback
service call, regardless of whether the new config was successfully derived from the service request.If, by accident, you call the service with a wrong configuration, the
__fromMesage__
function will fail since it won't be able to update thenew_config
, acording to server.h L219.The
__fromMesage__
function actually returns the result of the process, so I propose using the result to populate the service response correctly so the service caller can actually identify if the call failed.Current approach
Proposed solution
I am happy to submit a PR with the proposed solution.
The text was updated successfully, but these errors were encountered: