Your executeCallback did not set the goal to a terminalstatus. This is a bug in your ActionServer implementation. Fix your code! For now, the ActionServer will set this goal to aborted

Course Support ROS Basics In 5 Days (Python)
1

Please help to solve this issue.

2

Hi,

Sorry to hera you found an error in the code. Could you indicate exactly which exercise and what you would hope for it to do? Thanks

1 Like
3

I’ve got the same issue, I’m doing the Actions Quiz.
When I publish the goal this warning comes up on the main program.

5

This was because the CustomActionMsgResult was not used, I thought it wasn’t required because it was empty but I think it still needs an empty response to avoid the bug? Hope this helps anyone with the same issue :sweat_smile:

1 Like
6

When I try to use the CustomActionMsgResult I get an error that “SimpleActionServer instance has no attribute ‘publish_result’”
/K

7

Hi, can you give me a little more information about this error? What Unit are you working on, and can you share your code?

8

It was for the Unit 8 Actions Quiz. Even with the message I passed the quiz - since then I’ve played with the code a bit, so I don’t have the problematic version any longer. But thanks for checking.
/K

1 Like
9

Hi, I am in Unit 9 in the Actions Quiz part. I, too still have a similar problem but it does not affect my program that much. In order to avoid the warnings, since our ‘result’ in CustomActionMsg.action is empty, I wrote it something like this instead :

==== In my action server python file ====

if success:
       self._feedback.feedback = 'Taking off done'
       self._as.set_succeeded(self._feedback.feedback)

==== End =====

My take is that we don’t necessarily have to include the result just like how we did it in the fibonacci_action_server.py exercise.