--debug option should enable ERROR_REPORT.expert_mode
when trying to start bliss with a bug these days it does not really make a difference if the --debug
flag is set or not (at least in --no-tmux case).
To me the --debug
flag should enable the ERROR_REPORT.expert_mode
$ bliss -s test_session --no-tmux
__ __ __
|__) | | /__` /__`
|__) |__ | .__/ .__/
Welcome to BLISS version 1.2.0-202-g8a2bbeb3f running on rix (in bliss_dec19 Conda environment)
Copyright (c) 2015-2020 Beamline Control Unit, ESRF
-
Connected to Beacon server on rix (port /tmp/beacon_mch73_os.sock)
test_session: Loading config...
!!! === AttributeError: module 'bliss.shell.standard' has no attribute 'where' === !!! ( for more details type cmd 'last_error' )
vs.
$ bliss -s test_session --no-tmux --debug
__ __ __
|__) | | /__` /__`
|__) |__ | .__/ .__/
Welcome to BLISS version 1.2.0-202-g8a2bbeb3f running on rix (in bliss_dec19 Conda environment)
Copyright (c) 2015-2020 Beamline Control Unit, ESRF
-
Connected to Beacon server on rix (port /tmp/beacon_mch73_os.sock)
test_session: Loading config...
!!! === AttributeError: module 'bliss.shell.standard' has no attribute 'where' === !!! ( for more details type cmd 'last_error' )
(bliss_dec19) linus@rix:~/Documents/work/bcu/bliss_dec19$
in the second case I would expect the full python error stack.