tony-p

I have a similar issue (I think). I'm running inside a docker container with only port 8083 patched through, works fine on the local system, but streams don't start on...

if serving your own turn server, many ports need to be exposed, coturn example https://hub.docker.com/r/instrumentisto/coturn

Supporting the zeroMQ protocol would probably solve both issues as it sends/supplies the tree model, and can supply the action states updates. This would also remove the need for the...

Note this functionality was definitely available on v4.4.2 and has broken somewhere since then

Looking at those issues, this seems like a backwards compatibility issue for behavior trees generated with groot2. in older versions

Are you building with ROS2 by any chance? if so I have been adding https://github.com/tony-p/BehaviorTree.CPP/blob/e923c1fc412e2775cf1b5dbeae77cf7fd78525f0/cmake/ament_build.cmake#L7 for the pixi build to work. Can't remember exactly why I haven't upstreamed it, either...

when you run with pixi, are you running it within the pixi environement? pixi is built for a flavour of a conda virtual environment, so to run you should either...

I'm not a maintainer so can't push this further. My first thought was why not define the qos in the node implementation as it will typically be constant for a...

Handling different QoS configurations is something we've also hit up against. However I don't really understand the need to wait for a message. Personally I feel like the behaviour tree...

Yes it makes the tree a bit more verbose, but it keeps the usage pattern more consistent. There are always different opinions and usage patterns for things. Personally I am...