wxbanker crashed with TypeError in GetBalance()

[David D Lowe]

I had just created an empty account before restarting wxBanker.

$ sqlite3 /home/david/.local/share/bank.db "select * from accounts"
1|Censored|0|Censored|
2|Censored|0|Censored|
3|Censored|0|Censored|
4|Test|0|120.0|
5|\\|0||

As you can see, for some reason the last account doesn't have a balance saved, not even 0.

Traceback should be included as an attachment.

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: wxbanker 0.8.1~ppa1~10.10
ProcVersionSignature: Ubuntu 2.6.35-22.33-generic-pae 2.6.35.4
Uname: Linux 2.6.35-22-generic-pae i686
Architecture: i386
CrashDB: wxbanker
Date: Sat Oct 2 19:34:57 2010
ExecutablePath: /usr/bin/wxbanker
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
InterpreterPath: /usr/bin/python2.6
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/wxbanker
ProcEnviron:
 SHELL=/bin/bash
 LANG=en_GB.utf8
PythonArgs: ['/usr/bin/wxbanker']
SourcePackage: wxbanker
ThirdParty: True
Title: wxbanker crashed with TypeError in GetBalance()
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Michael Rooney (mrooney)]

That's very weird! Can you think of anything odd that happened, or you just created an account, restarted wxBanker, and this occurred? The merge proposal might fix it but seems like a work-around for the actual issue which is that something is passing in None as the balance somehow.

I'm confused as to how that row column could not have an entry, 'balance' is 'not null default 0.0' so it shouldn't be possible to be null. You weren't querying or manipulating the database in any other way, by chance?

[David D Lowe (flimm)]

No I wasn't. I was using different versions of wxbanker, one after each other. I tried quite hard to reproduce this bug with a fresh bank.db but couldn't.

[Michael Rooney (mrooney)]

Good luck, let me know if you need any advice or tips!