Ryan

> > I would expect `FROM_IMAGE` is set to `humble` when using VSCode on the humble branch. > > How would you expect to set the build arg dynamically, while...

I tried a very specific change to just change the `build.cacheFrom` argument, however the dockerfile still has an ARG for the ROS distro, and VSCode doesn't support build arguments in...

We have a path forward. I'd say once the next VSCode version is out of beta and released, we can add build arguments to specify a ros distro. https://github.com/microsoft/vscode-remote-release/issues/3545#issuecomment-1892274755

> This should now be possible @Ryanf55 right? Correct, feel free to submit a PR. I have other priorities right now.

Ok, so mostly it's working well, however there are times it seems the waypoint follower never terminates despite meeting the goal. ``` [component_container_isolated-6] [INFO] [1674671838.601573493] [controller_server]: Passing new path to...

I've just implemented the final part of setting total time taken back to 0 on completion using the follow waypoints goal status message. The one bug in the UI right...

> You have to rebase from main.. so that you have an updated copy of mergify.yaml in your branch.. Just rebased, still failing.

Hey there, 1) I got my head wrapped around the axle on the state machine and couldn't figure out exactly how to transition the state machine to the new "running"...

Ok for problem 2, I just manually copied the state machine through inspection to a state-machine capable renderer for markdown called mermaid. See below. Now that I've actually mapped out...

> getFollowWaypointsFeedbackLabel After trying this approach, I've run into the snag that there is mixed information between nav through poses and follow waypoints. The `toLabel` function used in both `getNavThroughPosesFeedbackLabel`...