Error in rmf_traffic_schedule_node about rmf_demos HOT 1 CLOSED

We've seen this issue popping up a few times for various users, but haven't been able to reproduce the issue reliably. This may be an opportunity for us to get some insight on what might be causing it.

Could you do me a favor and look at the contents of a hidden file called .rmf_schedule_node.yaml that will live in whatever directory you call ros2 launch ... from? (Presumably the file will be ~/rmf_ws/.rmf_schedule_node.yaml).

Then copy/paste the entire contents of that file into a gist, create a public gist and link us to it. Or if there's any reason you don't want to share the contents publicly, you could also send me an email with the file's contents, and I'll keep it confidential.

Being able to see the contents of that file might help us identify why this has been happening randomly for some users.

After you've shared the contents with us, you can simply delete that file and then everything should work fine again. You should also consider updating your rmf_internal_msgs, rmf_traffic, and rmf_ros2 repos by running git pull origin main in each of those folders inside of ~/rmf_ws/src/rmf/, because it's possible (but not confirmed) that this issue is related to this bug fix.

from rmf_demos.