-
Notifications
You must be signed in to change notification settings - Fork 32
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
Fix remaining issues in applications and demos from the updated spaceros base image #189
Conversation
1651588
to
fc0482c
Compare
I am trying to test #152, but that requires moveit2 docker which is failing on shall we test/push this one first to make life easier? |
fc0482c
to
bd6de91
Compare
@asimonov this should fix the nav2 build if you have a locally built space ros image. Still working on getting But yes for testing #152 you could just manually change the name of the starting image to use a locally built version of |
yes, I am using the locally built images. but it is getting confusing... basically if our ultimate test is to run moveit and rover demos that requires all the images to 1. be built, 2. be consistent. and they require different PRs to be brought to that state. if we could save branch tagged images and start merging PRs, that would alleviate confusion to some degree |
Ugh, yes sorry things have been in an odd state, but now that the main image is updated and pushed to Dockerhub, too things should be more clear? This PR should resolve the build issues on |
almost... git-lfs change on simulation broke my local build of docker/space_robots... space-ros/simulation#35 i think we need to test every PR on affected repos by running those 2 demos. because they effectively combine everything we have |
Erik, can you include the lfs setup into this PR as well? |
Ugh, in the interest of traceability I included that fix in #194, since that was broken by a separate change...
This is a big ask until we get some sort of automated infrastructure in place to at least pre-build those images. Or in an ideal worth a pre-build and a basic sanity check. But hopefully we can get that done sooner rather than later? |
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.
looks good. and it builds locally.
but i cannot test demos (mars rover and navigation) because of other issues (e.g. #194)
i suggest we merge all these PRs releated to fixing the build and then re-test the demos
c8ae621
to
a279715
Compare
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.
Can we break out the GitHub Actions version bumps into another issue/PR? Everything else is clearly related
a279715
to
843505b
Compare
843505b
to
2279408
Compare
Done. Squashed those changes out of the param change commits and updated. Everything else remains unchanged. I'll open a separate issue to update CI since there's more that would be helpful now that we have main available... |
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.
These code changes all make obvious sense to me. (which I say in lieu of testing)
The time is nigh! |
Resolves #161.
There are still issues building
main
for moveit and nav2 after migration of the base image build to the space-ros repo. This PR fixes them, includingAs the base
main
image is now pushed to GHCR, we should use that when building in CI. The change can be tested locally if you have access to the container registry (you must be logged in):Update:
Depends on space-ros/space-ros#220
Because the GHCR images are not public, we can temporarily point to the main branch in the docker registry. This can be tested with either
moveit2
ornav2
with: