drake-ros icon indicating copy to clipboard operation
drake-ros copied to clipboard
verified publisher icon RobotLocomotion

Improve `bazel_ros2_rules` error handling

Open hidmic opened this issue 4 years ago • 3 comments

Failure modes for bazel_ros2_rules are quite opaque, if at all traceable -- specially when it comes to errors during CMake configuration scraping. Overall UX needs improvement.

hidmic avatar Feb 21 '22 20:02 hidmic

FYI @EricCousineau-TRI. For instance, if some package upstream isn't exporting its dependencies properly, we're in for a fun archaeological trip down here.

hidmic avatar Feb 21 '22 20:02 hidmic

Oh nuts! Do you have concrete example of how opaque errors currently are? Perhaps via gist.github.com, or with a commit + mirrored tarball?

EricCousineau-TRI avatar Feb 21 '22 20:02 EricCousineau-TRI

See here. We basically have to cap noisy tracebacks, collect CMake server output to bundle it with any exception thrown, and repackage everything in the outermost try ... except block for human consumption.

We also shouldn't have packages that half export their dependencies :eyes:

hidmic avatar Feb 21 '22 21:02 hidmic