Browse Source
When raising generic Exception, window.on_error can't tell whether there was a programming error or we just want to communicate with the user. E | gui.qt.main_window.[default_wallet] | on_error Traceback (most recent call last): File "/home/user/wspace/electrum/electrum/gui/qt/util.py", line 832, in run result = task.task() File "/home/user/wspace/electrum/electrum/gui/qt/main_window.py", line 2900, in <lambda> task = lambda: self.network.run_from_another_thread( File "/home/user/wspace/electrum/electrum/network.py", line 358, in run_from_another_thread return fut.result(timeout) File "/usr/lib/python3.8/concurrent/futures/_base.py", line 439, in result return self.__get_result() File "/usr/lib/python3.8/concurrent/futures/_base.py", line 388, in __get_result raise self._exception File "/home/user/wspace/electrum/electrum/wallet.py", line 162, in sweep_preparations raise Exception(_('No inputs found.')) Exception: No inputs found.bip39-recovery
SomberNight
5 years ago
1 changed files with 2 additions and 2 deletions
Loading…
Reference in new issue