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 better is to return (Publisher, error) in this case and involve typical Go error handling mechanics than unconditionally die.
I'm building a service where ROS node can be started later, some functionality of it doesn't depend on ROS. But I cannot start when ROS master is not available because of os.Exit() in the rosgo.
The text was updated successfully, but these errors were encountered:
Current implementation calls
logger.Fatalf()
(andos.Exit()
inside) when it's not possible to create objects.For example:
The better is to return
(Publisher, error)
in this case and involve typical Go error handling mechanics than unconditionally die.I'm building a service where ROS node can be started later, some functionality of it doesn't depend on ROS. But I cannot start when ROS master is not available because of
os.Exit()
in therosgo
.The text was updated successfully, but these errors were encountered: