-
Notifications
You must be signed in to change notification settings - Fork 74
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use frontend group dependency & explicit dependencies in ros2launch #256
Use frontend group dependency & explicit dependencies in ros2launch #256
Conversation
@hidmic @wjwwood here's (along with ros2/launch#520) the solution I'm proposing based on your comments. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
Anyone have any idea why we have failures on Windows now? I didn't investigate, but it could be to new missing dependencies? |
Some |
Update: I cannot reproduce it on a plain Windows VM. Something's up with the CI Windows container. |
could this just be a flake? |
I don't see how. If it is a flake, then it is a bug underneath. |
yeah and
this is a bit confusing. |
It does indirectly through
|
yeah, in practice, so isn't that kind of problematic/isn't that the reason why the test is failing?
I don't understand why it only fails on Windows and why it seems to be working fine without this PR, and maybe I'm misunderstanding something, but this "undeclared" dependency seems problematic to me. Note that |
I re-ran the original Windows job with this PR and the launch PR, but with |
This might be related to |
You're absolutely right.
That's also right!
It could be. We need a Windows-specific explanation as to why |
I'll try to make time to look into it this week. |
Has anyone had a chance to look into this? |
I haven't had time yet unfortunately. I'll try to look into it tomorrow. |
Yeah, no pressure, just curious. |
I tried to reproduce and I couldn't either. I haven't had time to dig deeper. |
For some context, since Python 3.8, To work around this, we introduced that utility in I guess what's happening in this case is that the |
Signed-off-by: Christophe Bedard <bedard.christophe@gmail.com>
Signed-off-by: Christophe Bedard <bedard.christophe@gmail.com>
Signed-off-by: Christophe Bedard <bedard.christophe@gmail.com>
dbe2ac4
to
66c6d7e
Compare
Thanks for the info @jacobperron. I once again tried to reproduce and couldn't. Without being able to reproduce on my local machine, I'm not really sure how to proceed, especially since this is quite time-consuming for such a minor change. |
Yeah I simply rebased. Those CI jobs don't build/test the same packages as the jobs that failed above, like this one: https://ci.ros2.org/job/ci_windows/15054/ |
Oh sorry, I forgot to add ros2/launch#520. |
CI is green, so... I guess it's fixed‽ The issue, as I understood it, was slightly concerning, so I hope this doesn't come back to bite us. |
I think the issue was the same as ros2/rclpy#831 |
Closes #255
Requires ros2/launch#520
As suggested/discussed under ros2/launch#516 (comment), this uses a group dependency for the launch frontends and declares explicit dependencies on
launch_xml
andlaunch_yaml
forros2launch
.Using both a group dependency and hard/explicit dependencies allows this to work fine with binaries (with bloom) and also allows us to include any future launch frontend (or any user's custom frontend) in source builds. This is similar to how
rcl
depends on both thercl_logging_packages
group and the default logging implementation explicitly.Signed-off-by: Christophe Bedard bedard.christophe@gmail.com