hook stderr not being logged during debug-code

[Stuart Bishop]

If my hook is completely broken, for example a Python script failing with an import error, then I can't see what is going wrong when running 'juju debug-code'. When the hook runs, if you are quick you can see a tmux window briefly flicker into existance and exit. If you are not perceptive there is no visual indication that the hook ran at all, let alone failed. The juju logs do state that the hook failed, but no traceback or other details as stderr is not captured.

I suggest that the tmux windows do not automatically close, or close after a timeout. The point of running debug-code is you want to interactively debug the code, and the fact that your breakpoint was not hit or the dispatch script completely failed is important information.

[John A Meinel (jameinel)]

See things like:
https://unix.stackexchange.com/questions/17116/prevent-pane-window-from-closing-when-command-completes-tmux

There is a flag like 'remain-on-exit' though maybe we don't want to always remain on exit, but only remain if it would have exited too quickly.

[Pen Gale (pengale)]

Added charm-debugging tag, and triaged as Medium. I'd like to see us address this, probably as a general push to make things better for debugging charms. It's not on the docket for this cycle, however.

[Canonical Juju QA Bot (juju-qa-bot)]

This bug has not been updated in 2 years, so we're marking it Low importance. If you believe this is incorrect, please update the importance.