'Major error occurred when trying to execute a SQL statement' when clicking on inbox message #474

New Issue

2013-09-04T10:01:32+02:00

etataurov commented

2013-09-04 10:01:32 +02:00

(Migrated from github.com)

Just checkouted the latest version eff4edb8e8
subscribed to some channel.
I've got some new messages from timeserver (BM-BcbRqcFFSQUUmXFKsPJgVQPSiFA3Xash)
when i click on message, app crashes.

2013-09-04 13:58:15,984 - CRITICAL - Major error occurred when trying to execute a SQL statement within the sqlThread. Please tell Atheros about this error message or post it in the forum! Error occurred while trying to execute statement: "SELECT toaddress, read FROM inbox WHERE msgid=?" Here are the parameters; you might want to censor this data with asterisks (***) as it can contain private information: (('\x8b\xb01+\xc1\xb9.\x10\x823\x87\xfc9\x8e\x81P^O\xac\xa1\x19\xb2)\xb3\xe4\xf8\xaf\xb7\x8fF\x03\xd0',),). Here is the actual error message thrown by the sqlThread: Error binding parameter 0 - probably unsupported type.
'pubkey' from Peer(host='173.59.250.105', port=8444)
2013-09-04 13:58:15,985 - CRITICAL - This program shall now abruptly exit!

Just checkouted the latest version eff4edb8e85c5534a2e573cab97fe96242a8bcf2 subscribed to some channel. I've got some new messages from timeserver (BM-BcbRqcFFSQUUmXFKsPJgVQPSiFA3Xash) when i click on message, app crashes. 2013-09-04 13:58:15,984 - CRITICAL - Major error occurred when trying to execute a SQL statement within the sqlThread. Please tell Atheros about this error message or post it in the forum! Error occurred while trying to execute statement: "SELECT toaddress, read FROM inbox WHERE msgid=?" Here are the parameters; you might want to censor this data with asterisks (***) as it can contain private information: (('\x8b\xb01+\xc1\xb9.\x10\x823\x87\xfc9\x8e\x81P^O\xac\xa1\x19\xb2)\xb3\xe4\xf8\xaf\xb7\x8fF\x03\xd0',),). Here is the actual error message thrown by the sqlThread: Error binding parameter 0 - probably unsupported type. 'pubkey' from Peer(host='173.59.250.105', port=8444) 2013-09-04 13:58:15,985 - CRITICAL - This program shall now abruptly exit!

afiskon commented

2013-09-04 14:14:50 +02:00

(Migrated from github.com)

I personally solved that issue following way:

cd ~/PyBitmessage
git reset --hard 7ad8ce7e1b

To developers: you shold probably use branches and tags. Regular users should use software from stable, well-tested branch (which, actually, master supposed to be).

I personally solved that issue following way: cd ~/PyBitmessage git reset --hard 7ad8ce7e1bd997ed8afabcf524597847941bc712 To developers: you shold probably use branches and tags. Regular users should use software from stable, well-tested branch (which, actually, master supposed to be).

Atheros1 commented

2013-09-04 18:55:16 +02:00

(Migrated from github.com)

Thank you very much for reporting this.

Atheros1 commented

2013-09-04 18:57:37 +02:00

(Migrated from github.com)

@afiskon Indeed, master should be stable all the time. This bug slipped past some people. Releases (which have a new version number) will be marked with tags from now on.

This repo is archived. You cannot comment on issues.