LBRY-Vault/electrum/plugins
SomberNight dace2e5495
trezor: don't let bridge transport failing block all other transports
[trezor] connecting to device at bridge:hid...
[trezor] connected to device at bridge:hid...
Traceback (most recent call last):
  File "...\electrum\electrum\base_wizard.py", line 255, in choose_hw_device
    u = devmgr.unpaired_device_infos(None, plugin, devices=scanned_devices)
  File "...\electrum\electrum\plugin.py", line 501, in unpaired_device_infos
    client = self.create_client(device, handler, plugin)
  File "...\electrum\electrum\plugin.py", line 374, in create_client
    client = plugin.create_client(device, handler)
  File "...\electrum\electrum\plugins\trezor\trezor.py", line 124, in create_client
    client = self.client_class(transport, handler, self)
  File "...\electrum\electrum\plugins\trezor\client.py", line 7, in __init__
    ProtocolMixin.__init__(self, transport=transport)
  File "...\Python36-32\lib\site-packages\trezorlib\client.py", line 444, in __init__
    self.init_device()
  File "...\Python36-32\lib\site-packages\trezorlib\client.py", line 454, in init_device
    self.features = expect(proto.Features)(self.call)(init_msg)
  File "...\Python36-32\lib\site-packages\trezorlib\client.py", line 115, in wrapped_f
    ret = f(*args, **kwargs)
  File "...\Python36-32\lib\site-packages\trezorlib\client.py", line 129, in wrapped_f
    client.transport.session_begin()
  File "...\Python36-32\lib\site-packages\trezorlib\transport\__init__.py", line 42, in session_begin
    self.open()
  File "...\Python36-32\lib\site-packages\trezorlib\transport\bridge.py", line 69, in open
    raise TransportException('trezord: Could not acquire session' + get_error(r))
trezorlib.transport.TransportException: trezord: Could not acquire session (error=400 str=wrong previous session)
[DeviceMgr] error getting device infos for trezor: trezord: Could not acquire session (error=400 str=wrong previous session)
2018-11-08 17:07:05 +01:00
..
audio_modem file reorganization with top-level module 2018-07-13 14:01:37 +02:00
coldcard coldcard: fix spending when there is no change 2018-11-06 16:17:18 +01:00
cosigner_pool rename crypto.Hash to sha256d 2018-10-25 22:28:24 +02:00
digitalbitbox rename crypto.Hash to sha256d 2018-10-25 22:28:24 +02:00
email_requests file reorganization with top-level module 2018-07-13 14:01:37 +02:00
greenaddress_instant transaction: don't convert p2pk to p2pkh address when displaying 2018-10-01 04:58:26 +02:00
hw_wallet kill old-style namedtuples 2018-10-28 00:28:29 +02:00
keepkey split bip32 from bitcoin.py 2018-10-25 22:20:33 +02:00
labels rm aiosafe decorator. instead: log_exceptions and ignore_exceptions 2018-10-12 18:36:48 +02:00
ledger split bip32 from bitcoin.py 2018-10-25 22:20:33 +02:00
revealer change prng, add warning against encrypting multiple secrets (#4649) 2018-08-22 22:25:12 +02:00
safe_t split bip32 from bitcoin.py 2018-10-25 22:20:33 +02:00
trezor trezor: don't let bridge transport failing block all other transports 2018-11-08 17:07:05 +01:00
trustedcoin split bip32 from bitcoin.py 2018-10-25 22:20:33 +02:00
virtualkeyboard file reorganization with top-level module 2018-07-13 14:01:37 +02:00
__init__.py file reorganization with top-level module 2018-07-13 14:01:37 +02:00
README file reorganization with top-level module 2018-07-13 14:01:37 +02:00

Plugin rules:

 * The plugin system of Electrum is designed to allow the development
   of new features without increasing the core code of Electrum.

 * Electrum is written in pure python. if you want to add a feature
   that requires non-python libraries, then it must be submitted as a
   plugin. If the feature you want to add requires communication with
   a remote server (not an Electrum server), then it should be a
   plugin as well. If the feature you want to add introduces new
   dependencies in the code, then it should probably be a plugin.

 * We expect plugin developers to maintain their plugin code. However,
   once a plugin is merged in Electrum, we will have to maintain it
   too, because changes in the Electrum code often require updates in
   the plugin code. Therefore, plugins have to be easy to maintain. If
   we believe that a plugin will create too much maintenance work in
   the future, it will be rejected.

 * Plugins should be compatible with Electrum's conventions. If your
   plugin does not fit with Electrum's architecture, or if we believe
   that it will create too much maintenance work, it will not be
   accepted. In particular, do not duplicate existing Electrum code in
   your plugin.

 * We may decide to remove a plugin after it has been merged in
   Electrum. For this reason, a plugin must be easily removable,
   without putting at risk the user's bitcoins. If we feel that a
   plugin cannot be removed without threatening users who rely on it,
   we will not merge it.