KeyError in wallet.get_addr_utxo
Open
Nobody has claimed this yet.
bug 🐞
topic-wallet 👛
- Dominant language
- Python
- Stars
- 8.6k
- Forks
- 3.5k
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 61
Description
Crash Report
This crash report was reported through the automatic crash reporting system 🤖
Traceback
File "electrum\gui\qt\main_window.py", line 763, in update_tabs
File "electrum\gui\qt\util.py", line 521, in update
File "electrum\gui\qt\utxo_list.py", line 44, in on_update
File "electrum\address_synchronizer.py", line 470, in f
File "electrum\address_synchronizer.py", line 766, in get_utxos
File "electrum\address_synchronizer.py", line 714, in get_addr_utxo
KeyError: 'b753b490d136936ade88f9442a9510d14196d01eb1cc7dab3bec0d854ede1020:1'
Reporter
This issue was reported by 15 user(s):
| Electrum Version | Python Version | Operating System | Wallet Type | Locale | Stack |
|---|---|---|---|---|---|
| 3.2.3 | 3.6.6 (v3.6.6:4cf1f54eb7, Jun 27 2018, 02:47:15) [MSC v.1900 32 bit (Intel)] | Windows-8.1-6.3.9600-SP0 | standard | de_DE | ℹ |
| 3.2.3 | 3.6.4 (default, Mar 1 2018, 10:42:21) [GCC 5.3 20151204] | Android 7.1.1 on ZTE draco (Z835V2.0.0B12) | imported | ? | ℹ |
| 3.2.3 | 3.6.6 (v3.6.6:4cf1f54eb7, Jun 27 2018, 02:47:15) [MSC v.1900 32 bit (Intel)] | Windows-10-10.0.17134-SP0 | 2fa | sl_SI | ℹ |
| 3.2.3 | 3.6.6 (v3.6.6:4cf1f54eb7, Jun 27 2018, 02:47:15) [MSC v.1900 32 bit (Intel)] | Windows-7-6.1.7601-SP1 | standard | en_US | ℹ |
| 3.3.2 | 3.6.7 (v3.6.7:6ec5cf24b7, Oct 20 2018, 12:45:02) [MSC v.1900 32 bit (Intel)] | Windows-10-10.0.10240-SP0 | standard | en_US | ℹ |
| 3.3.2 | 3.6.7 (v3.6.7:6ec5cf24b7, Oct 20 2018, 12:45:02) [MSC v.1900 32 bit (Intel)] | Windows-10-10.0.10240-SP0 | standard | en_US | ℹ |
| 3.3.2 | 3.6.7 (v3.6.7:6ec5cf24b7, Oct 20 2018, 12:45:02) [MSC v.1900 32 bit (Intel)] | Windows-7-6.1.7601-SP1 | standard | zh_CN | ℹ |
| 3.3.2 | 3.6.7 (v3.6.7:6ec5cf24b7, Oct 20 2018, 12:45:02) [MSC v.1900 32 bit (Intel)] | Windows-7-6.1.7601-SP1 | standard | zh_CN | ℹ |
| 3.3.4 | 3.6.8 (tags/v3.6.8:3c6b436a57, Dec 23 2018, 23:31:17) [MSC v.1916 32 bit (Intel)] | Windows-10-10.0.17763 | standard | sv_SE | ℹ |
| 3.3.4 | 3.6.8 (tags/v3.6.8:3c6b436a57, Dec 23 2018, 23:31:17) [MSC v.1916 32 bit (Intel)] | Windows-7-6.1.7601-SP1 | standard | it_IT | ℹ |
| 3.3.4 | 3.6.8 (tags/v3.6.8:3c6b436a57, Dec 23 2018, 23:31:17) [MSC v.1916 32 bit (Intel)] | Windows-10-10.0.17134-SP0 | standard | en_US | ℹ |
| 3.3.2 | 3.6.7 (v3.6.7:6ec5cf24b7, Oct 20 2018, 12:45:02) [MSC v.1900 32 bit (Intel)] | Windows-10-10.0.17763-SP0 | standard | de_DE | ℹ |
| 3.3.8 | 3.6.8 (default, Jan 14 2019, 11:02:34) [GCC 8.0.1 20180414 (experimental) [trunk revision 259383]] | Linux-4.15.0-59-generic-x86_64-with-Ubuntu-18.04-bionic | imported | ru_RU | ℹ |
| 3.3.8 | 3.7.1 (default, Jul 11 2019, 14:15:43) [Clang 6.0.2 (https://android.googlesource.com/toolchain/clang 183abd29fc496f55 | Android 6.0.1 on samsung j3xlte (lineage_j3xnlte-userdebug 6.0.1 MOB31T c708f55cf7 test-keys) | standard | en_US | ℹ |
| 3.3.8 | 3.6.4 (default, Feb 28 2018, 03:24:19) [GCC 4.2.1 Compatible Apple LLVM 8.0.0 (clang-800.0.42.1)] | Darwin-19.0.0-x86_64-i386-64bit | imported | ? | ℹ |
Additional Information
i really don't know
i really don't know
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with electrum/address_synchronizer.py, especially get_addr_utxo at line 714 and get_utxos at line 766, then trace the callers in electrum/gui/qt/utxo_list.py and main_window.py. Reproduce the reported wallet update path and identify why the referenced transaction output is missing; done means the update no longer raises this KeyError.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100