[rmf_traffic_schedule_node]: Failed to correctly load participant registry: yaml-cpp: error at line 15, column 11: bad conversion

[jamietjx]

I tried to ros2 run the traffic schedule node and got this error. I am trying to integrate rmf_core with the fleet_adapter_mir.

[Yadunund]

This repository is archived. We have migrated our development to a new organization page. Please follow the instructions there to install the latest RMF packages. If you still encounter a problem, please open a ticket there.

[mxgrey]

First, this osrf/rmf_core repo is considered deprecated, so I recommend shifting your attention to the new open-rmf organization: https://github.com/open-rmf/rmf. The recommended place for general discussions on RMF is here.

The issue you're reporting was a known issue in an older version of RMF: open-rmf/rmf_ros2#20

It should be fixed now by this PR, but you'll need to migrate to the open-rmf repos to get the fix.

In the meantime, there are some steps you could take to help us confirm that the latest version of RMF is fixed.

1. Look for a file named .rmf_schedule_node.yaml in the directory that you launch RMF from
2. Create a gist
3. Copy/paste the contents of .rmf_schedule_node.yaml into the gist
4. Save the gist and send us the link to it
5. Delete the file .rmf_schedule_node.yaml on your own computer

After that, building and running the latest version of RMF should prevent this issue from happening again.

[jamietjx]

Thank you so much for your help.

[jamietjx]

The problem is solved after deleting the file .rmf_schedule_node.yaml. Here is the link to the gist:https://gist.github.com/jamietjx/ad390d81d357bddd195c4cf26cdb4df5 [https://github.githubassets.com/images/modules/gists/gist-og-image.png]<https://gist.github.com/jamietjx/ad390d81d357bddd195c4cf26cdb4df5> [FATAL] [1623770339.998705264] [rmf_traffic_schedule_node]: Failed to correctly load participant registry: yaml-cpp: error at line 59, column 11: bad conversion<https://gist.github.com/jamietjx/ad390d81d357bddd195c4cf26cdb4df5> [FATAL] [1623770339.998705264] [rmf_traffic_schedule_node]: Failed to correctly load participant registry: yaml-cpp: error at line 59, column 11: bad conversion - .rmf_schedule_node.yaml gist.github.com

…

________________________________ From: Grey ***@***.***> Sent: Tuesday, 15 June 2021 11:51 AM To: osrf/rmf_core ***@***.***> Cc: Jamie Tan ***@***.***>; Author ***@***.***> Subject: Re: [osrf/rmf_core] [rmf_traffic_schedule_node]: Failed to correctly load participant registry: yaml-cpp: error at line 15, column 11: bad conversion (#326) First, this osrf/rmf_core repo is considered deprecated, so I recommend shifting your attention to the new open-rmf organization: https://github.com/open-rmf/rmf. The recommended place for general discussions on RMF is here<https://github.com/open-rmf/rmf/discussions>. The issue you're reporting was a known issue in an older version of RMF: open-rmf/rmf_ros2#20<open-rmf/rmf_ros2#20> It should be fixed now by this PR<open-rmf/rmf_ros2#22>, but you'll need to migrate to the open-rmf repos to get the fix. In the meantime, there are some steps you could take to help us confirm that the latest version of RMF is fixed. 1. Look for a file named .rmf_schedule_node.yaml in the directory that you launch RMF from 2. Create a gist<https://gist.github.com/> 3. Copy/paste the contents of .rmf_schedule_node.yaml into the gist 4. Save the gist and send us the link to it 5. Delete the file .rmf_schedule_node.yaml on your own computer After that, building and running the latest version of RMF should prevent this issue from happening again. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub<#326 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ASQP3Q5LFAN6V53CGT6HEILTS3E5FANCNFSM46WKKE5Q>. This e-mail and any attachments are only for the use of the intended recipient and may contain material that is confidential, privileged and/or protected by the Official Secrets Act. If you are not the intended recipient, please delete it or notify the sender immediately. Please do not copy or use it for any purpose or disclose the contents to any other person.

[mxgrey]

Thanks for providing the file; that helps me confirm my belief that this issue is fixed in the latest version.

Note that if you only delete the .rmf_schedule_node.yaml file, the problem will only be solved temporarily. The bug that corrupted that file will likely happen again unless you update to the latest version of RMF.