search

bitshares / bitshares1-webwallet

Web Interface for BitShares Wallets 0.x (before 2015-10-13)
The Unlicense
35 stars 53 forks source link

no transactions showing at all .. though in the console: "JSON Parse error: Unterminated string" #621

Open xeroc opened 9 years ago

xeroc commented 9 years ago

https://bitsharestalk.org/index.php?topic=14313.msg186293#msg186293

I have some transaction details .. not all .. and those I got pm'ed look all fine .. nothing strange encoding-wise

vikramrajkumar commented 9 years ago

I have seen other reports of this as well.

dnotestein commented 9 years ago

I've got this problem with my current 0.61 GUI client. Transaction history displays from console, so I think it's a GUI problem (or rather, a communication problem between GUI and console client). The transaction history used to display OK on the dashboard, so it seems likely it is caused by some details of a transaction that started confusing the GUI, or the transaction history got too big for the GUI to handle. As I'm seeing the same "Unterminated string" message, my best guess is the JSON result is too big.

Methodise commented 9 years ago

I also have 'no transactions' in my dashboard view, although the problem is intermittent. I also have no preservation of my logout timeout preferences.

But running 'history' in the GUI shows plenty.

I'm fully synced with version 0.6.1 for Mac.

vikramrajkumar commented 9 years ago

Another report (unsure what version): https://bitsharestalk.org/index.php?topic=14313.msg187862#msg187862

valzav commented 9 years ago

Based on this https://bitsharestalk.org/index.php?topic=14545.msg190676#msg190676 I can conclude that transactions history json returned to the gui is malformatted or maybe as dnotestein suggested it's too big to be parsed by QT webkit's js implementation

valzav commented 9 years ago

He has only 41 in transactions history for this account, so I don't think this is because of the too big json. One of the memos is " ┐╢╔►╛┘t\Y²ΦìδÑ.µqu# " - probably this is the reason it fails to parse json. Can we escape memos on the server side?

dnotestein commented 9 years ago

I've had another thought about it, also, since then. I'm wondering if it's not possible that we're seeing a double value expressed in scientific notation (e.g 0.45e-3) and that the json parser is having problems with parsing it (I know that at least in the past, fc's parser couldn't handle exponentials).

vikramrajkumar commented 9 years ago

Still happening: https://bitsharestalk.org/index.php?topic=15420.msg198917#msg198917

It doesn't seem like right now fc supports a good way to escape bad strings like the above.