Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

ROS2 Action Server getting info of the client node name and the goal priority

Aperta
#2,832 5 commenti 0 reazioni 1 assegnatario Vedi su GitHub

@fujitatomoya ci sta già lavorando.

Dal 9/5/2025.

Valutazione

Questa issue non è ancora stata valutata.

Descrizione

backlog enhancement more-information-needed
Description

Hello!

Thank you all for such great work. Most of the times in real applications, the action server should show different behaviour depending on the type of the node, for instance, an emergency movement in joints should prevail any motion it is executing or any motion it will receive in future. However, there is no clear line of priority setting in the goals, and i believe it shouldn't be particular to a specific action. If not, most of the released packages needed to be modified inorder to handle this kind of functionality.

Regarding the node name, it would be interesting for the action server to know from whom it is receiving the goal, this information can be used by the server to accept or reject goals. For instance, I want only authorized applications be able to send goals to the hardware and not anyone, inorder to avoid any uncontrolled movements

Motivation

The motivation is for the hardware based ros2 controllers the action server will need to handle the resource sharing and this way it can give critical applications more preference than any kind of application sending random movement (or) a robot performing human robot interaction and then it being preempted as navigation needs the head of the robot. These kind of cases are pretty usual in any application.

I would like to hear your views.

Thank you

Design / Implementation Considerations

No response

Additional Information

No response

Lingua principale
C++
Stelle
805
Fork
564
Merge medio
1g 22h
PR unite (30g)
21

Guida per i contributori

Apri la guida per i contributori

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di ros2/rclcpp

Tutte le issue di ros2/rclcpp

Issue simili

Altre issue su C++

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.