Philipp Schillinger

The only way I found to achieve the reported observations was the case that one of the ROS packages (not necessarily containing states or behaviors) would have a malformed package.xml....

So do I correctly understand that version 1.2.2 / 2.2.2 do not work, also not after re-installing, but 1.2.1 / 2.2.1 do work as expected?

The referenced update function is automatic and works in the background. Using Ubuntu's mechanism to receive updates about changed files, the state files are automatically re-loaded when such notifications are...

I indeed found an issue that prevented the automated state reloading when using the Python parser: Since Python internally caches any previously imported module and does not reload it again,...

Thanks for the pointer @dcconner! First as a disclaimer, I'm not yet familiar with every single technical detail of the `ros2-devel` and `ros2-pre-release` branches, so I might need to revise...

Thanks for pointing out! This is specific to ROS 2 and I think it comes from the difference in how the workspace installation is handled there in comparison to ROS...

The binary jobs for `flexbe_app` also didn't properly run before, so we always had them excluded. Unfortunately, I don't have a lot of experience with this, but this old PR...

Is the workspace sourced in your bashrc? Does this also happen when your run roscd flexbe_states rosrun flexbe_app run_app -o # in the same terminal In general, the way that...

That's an interesting observation and could indeed be related. I will look further into this.

Still not sure what could be the issue for not finding states in kinetic... Regardless of this, @Sinchiguano I would recommend you to use melodic if possible. @dcconner any idea...