Closed tsaubergine closed 3 months ago
Edge case if the tool can't find jaiabot-status:
ERROR executing:
"jaiabot-status" "--binary=jaia status"
Ensure that Segmentation fault (core dumped)
Edge case if the tool can't find jaiabot-status:
ERROR executing: "jaiabot-status" "--binary=jaia status" Ensure that Segmentation fault (core dumped)
Oops. Thanks for catching this!
Fixed at https://github.com/GobySoft/goby3/pull/321/files, which will be part of Goby 3.1.6 whenever that happens.
With that fix you get a more sensible:
ERROR executing:
"jaiabot-status" "--binary=jaia status"
Ensure that jaiabot-status is on your path and is executable.
Application:: uncaught exception: Action was expected to be handled by external tool
terminate called after throwing an instance of 'goby::Exception'
what(): Action was expected to be handled by external tool
Implements https://jaia-innovation.atlassian.net/browse/JAIA-194?atlOrigin=eyJpIjoiOTFhNmYxN2Q4YjE2NDUwYzhjN2UwMTg1ZTAwMTgyYWUiLCJwIjoiaiJ9
I also fixed a bug in jaiabot-debian while testing this PR: https://github.com/jaiarobotics/jaiabot-debian/pull/62
Details:
jaia version
by readingapt-cache policy jaiabot-embedded
. This will also add it to jaiabot_metadata as these share the same functionjaia version
by readingapt-cache policy moos-ivp-apps
jaia version
instead of reading files in/etc/jaiabot
directly.New end section of
75-jaiabot-status
when installed usingjaiabot-embedded
deb package:or via git based build: