Topic 'keyboard.pressed' has non-power-of-2 capacity 0 error

[gelanchez]

I'm encountering an intermittent RuntimeError where topic keyboard.pressed reports a "non-power-of-2 capacity 0" and claims it was "created with an old version." This happens randomly during a two-node Python producer/consumer setup, even when I am certain no other HORUS instances are running. Most notably, the error persists even after I manually delete the /dev/shm/horus folder. What could be causing this?

[neos-builder]

hmnn, this is a bug in race condition in horus_core for consumer to read the file, thanks for discover this out.

[gelanchez]

Is it related to the python bindings? The RuntimeError happens in the keyboard node, before the consumer is created. Would that help if the consumer is initialized first? Is there an easy way to control that using multiple files?

I'm planning to start using more Rust in my project, as it seems more robust and feature rich. I can keep raising the minor bugs I'm seeing as I progress further.

Thanks!

[neos-builder]

It is in the shared memory created itself, the dev/shm is created as runtime, so the race might be the consumer read when there is no producer yet, I will make a gate and prevent magic number and kind of waiting, this might be an edge case. The performance nevertheless will remain the same, no tradeoffs.

[gelanchez]

Thanks, that sounds sensible!

[neos-builder]

I'm currently working on the bridge and converter for ros2 and testing, so next commit with the fix might be longer than expected

[gelanchez]

Thanks. I'm looking forward to trying out the next versions; I love the framework and its ideas! Happy to help out on its development :-)