Skip to content

Conversation

@Timple
Copy link
Contributor

@Timple Timple commented Feb 13, 2024

Just like rclcpp and ros1, allow action servers without execute callback.

Example like:

  • Display a message until a button is pressed
  • Actuate a motor until an endstop is reached

are typical cases where an action is succeeded based on information outside of the execute_cb.

It makes more sense to succeed these from outside the execute_cb in this case. And this would be in line with ros1 and rclcpp where this is possible.

I kept the execute_callback in args for backwards compatibility.

@Timple Timple force-pushed the do-not-force-executive-callback branch from d6f14c9 to 0dcf078 Compare February 13, 2024 18:10
@Timple Timple force-pushed the do-not-force-executive-callback branch from ac385b9 to d6163dc Compare February 14, 2024 16:57
Copy link
Collaborator

@fujitatomoya fujitatomoya left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@Timple thanks for the contribution.

i think this is reasonable and aligns with rclcpp, but i would like to have another review from maintainers.

@Timple
Copy link
Contributor Author

Timple commented Feb 22, 2024

Alright, we'll wait for those 🙂

@Timple
Copy link
Contributor Author

Timple commented Mar 19, 2024

Subtle ping 🙂

@Timple
Copy link
Contributor Author

Timple commented Apr 12, 2024

Sorry for subtle bump again, but Jade is coming up. And I'm afraid breaking changes won't be accepted anymore soon.

@fujitatomoya
Copy link
Collaborator

@clalancette @sloretz @ahcorde either of you, can you take a look at this? i think this is reasonable and more flexibility for rclpy client.

@fujitatomoya
Copy link
Collaborator

@Timple can you rebase this to rolling? almost 100 commits are behind.

@Timple Timple force-pushed the do-not-force-executive-callback branch from d6163dc to 0cf2d64 Compare April 14, 2024 08:21
@Timple Timple changed the base branch from iron to rolling April 14, 2024 08:21
@Timple
Copy link
Contributor Author

Timple commented Apr 14, 2024

@Timple can you rebase this to rolling? almost 100 commits are behind.

Done!

@Timple Timple force-pushed the do-not-force-executive-callback branch from 0cf2d64 to 26a7fdc Compare April 14, 2024 08:23
@ros-discourse
Copy link

This pull request has been mentioned on ROS Discourse. There might be relevant details there:

https://discourse.ros.org/t/upcoming-feature-freeze-for-ros-2-jazzy-jalisco-on-15th-april-2024/37075/2

@Timple
Copy link
Contributor Author

Timple commented Apr 29, 2024

So I missed the jazzy release 😿

But this PR had some proper traction. Can we still get this in rolling?

If everybody is very busy doing release stuff for jazzy, I also fully understand. Then I'll apply some sort of exponential backoff to my pings 🙂

@fujitatomoya
Copy link
Collaborator

@Timple sorry we missed this to jazzy. i will start the CI.

CC: @sloretz

@fujitatomoya
Copy link
Collaborator

CI:

  • Linux Build Status
  • Linux-aarch64 Build Status
  • Windows Build Status

@Timple
Copy link
Contributor Author

Timple commented May 16, 2024

It's green! 😄

@fujitatomoya
Copy link
Collaborator

@sloretz @clalancette friendly ping.

@Timple
Copy link
Contributor Author

Timple commented Jun 25, 2024

Joehoe ❤️

Copy link
Contributor

@ahcorde ahcorde left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't know the status of this PR or if this is still relevant, but I can see some conflicts

@Timple
Copy link
Contributor Author

Timple commented Oct 1, 2025

Well... Only if I can get some guarantee that it will be merged any time soon after fixing it :D

@ahcorde
Copy link
Contributor

ahcorde commented Oct 1, 2025

Well... Only if I can get some guarantee that it will be merged any time soon after fixing it :D

Sure, I will review it

@fujitatomoya
Copy link
Collaborator

@Mergifyio rebase

@mergify
Copy link
Contributor

mergify bot commented Oct 2, 2025

rebase

☑️ Nothing to do, the required conditions are not met

  • -conflict [📌 rebase requirement]
  • -closed [📌 rebase requirement]
  • queue-position = -1 [📌 rebase requirement]
  • any of:
    • #commits > 1 [📌 rebase requirement]
    • #commits-behind > 0 [📌 rebase requirement]
    • -linear-history [📌 rebase requirement]

@Timple
Copy link
Contributor Author

Timple commented Oct 2, 2025

That would have been great if that fixed it :).

The rebase should be fairly trivial but I won't get to this until next week. So if someone wants to give it a go..

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants