Skip to content

Conversation

@ivanpauno
Copy link
Collaborator

@ivanpauno ivanpauno commented Aug 19, 2020

(edit) #10 has already been merged.

This PR is build on top of #10.

It adds a new publisher event status: OfferedQosIncompatible.
That new event status is used to test the executor code in #10, which surprisingly works without changes.

There are some other cosmetic changes here.

I will rebase and redirect the PR to feature/events when #10 gets merged.

@ivanpauno ivanpauno added the enhancement New feature or request label Aug 19, 2020
@ivanpauno ivanpauno requested a review from jacobperron August 19, 2020 16:14
@ivanpauno ivanpauno self-assigned this Aug 19, 2020
@jacobperron
Copy link

surprisingly works without changes.

😂

Copy link

@jacobperron jacobperron left a comment

Choose a reason for hiding this comment

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

Besides the minor comments above, this LGTM

Signed-off-by: Ivan Santiago Paunovic <[email protected]>
@ivanpauno ivanpauno force-pushed the ivanpauno/add-offered-qos-incompatible-event branch from 9951769 to d7ad984 Compare August 20, 2020 13:06
@ivanpauno ivanpauno changed the base branch from ivanpauno/events-executor-support to feature/events August 20, 2020 13:06
@ivanpauno ivanpauno marked this pull request as ready for review August 20, 2020 13:08
@ivanpauno
Copy link
Collaborator Author

I have rebased feature/events against foxy-devel, and this branch against feature/events.
In that way, we can see CI being exercised now 😃 .

Signed-off-by: Ivan Santiago Paunovic <[email protected]>
Signed-off-by: Ivan Santiago Paunovic <[email protected]>
@ivanpauno
Copy link
Collaborator Author

ivanpauno commented Aug 20, 2020

@jacobperron there are some event statuses that we want but are not available in foxy (e.g. message lost), should we create a galactic-devel branch?

(edit) that should be done after completing basic event handling support in the foxy branch

@ivanpauno
Copy link
Collaborator Author

Unrelated, but I want to get rid of all stale branches.
Do we need to keep some of them or can I delete them all?

Signed-off-by: Ivan Santiago Paunovic <[email protected]>
@ivanpauno ivanpauno merged commit f36782a into feature/events Aug 20, 2020
@ivanpauno ivanpauno deleted the ivanpauno/add-offered-qos-incompatible-event branch August 20, 2020 15:48
@jacobperron
Copy link

@ivanpauno

there are some event statuses that we want but are not available in foxy (e.g. message lost), should we create a galactic-devel branch?

Yeah, feel free to create a galatic-devel branch when the time is right.

Unrelated, but I want to get rid of all stale branches.

Go ahead and delete stale branches 👍

ivanpauno added a commit that referenced this pull request Aug 31, 2020
ivanpauno added a commit that referenced this pull request May 17, 2021
ivanpauno added a commit to ros2-java/ros2_java that referenced this pull request Jan 14, 2022
ivanpauno added a commit to ros2-java/ros2_java that referenced this pull request Jan 25, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants