0.4.6 has a bug with transaction history, Users on that please upgrade to 0.4.7

[bytemaster]

Upgraded to 0.4.7 crashes upon launch?

Need more info to debug that one....  OS?  Run in XP Service Pack 3 compatibility mode?

Managed to launch it. Says database could be corrupted..ok I proceeded .. then I get this ..

RPC Server Error: In method 'wallet_get_info': Key Not Found (6)

However, I am now syncing with the network.

Ok.. once you are in sync the key not found error will go away.

[Bitshark]

Upgraded to 0.4.7 crashes upon launch?

Need more info to debug that one....  OS?  Run in XP Service Pack 3 compatibility mode?

Managed to launch it. Says database could be corrupted..ok I proceeded .. then I get this ..

RPC Server Error: In method 'wallet_get_info': Key Not Found (6)

However, I am now syncing with the network.

[bytemaster]

Upgraded to 0.4.7 crashes upon launch?

Need more info to debug that one....  OS?  Run in XP Service Pack 3 compatibility mode?

[Bitshark]

Upgraded to 0.4.7 crashes upon launch?

[DACSunlimited]

0.4.7 is also not stable, crashed 2 time within 1day, issue has been raised via github.

Delegates, please keep an eye on your delegates status(get notification or hot-standby) before the next stable version come out.

[crazybit]

0.4.7 is also not stable, crashed 2 time within 1day, issue has been raised via github.

[emski]

I've had no crashes with any version till 0.4.6 (inclusive).
However 0.4.7 crashed with segmentation fault after a day running properly.
I'll run it under gdb in order to catch the issue if it happens again.
The crashed client was a delegate with about 40 connections.
The seed node has 100+ connections and no issues yet.

[vikram]

Not sure if this has been fixed in 4.7 but in 4.5 when exporting the wallet and then trying to import it back I got this error:

Looking into it: https://github.com/BitShares/bitshares_toolkit/issues/675

Can anyone confirm whether or not backup import works correctly on Mac GUI or Linux command line? I suspect the problem is only on Windows.

I have found the problem and backup creation on Windows will be fixed in 0.4.8.

To recover your existing backup, open the backup file in a text editor like Notepad and scroll all the way to the end. There is an extra comma at the end of the file; the last two lines will look like this:

Code Select Expand


},
]


Delete that comma and save the file, and let us know if you can successfully import after doing this.

[solaaire]

The update fixed my transaction history and the client is working fine on my end. Thanks!

[vikram]

Not sure if this has been fixed in 4.7 but in 4.5 when exporting the wallet and then trying to import it back I got this error:

Looking into it: https://github.com/BitShares/bitshares_toolkit/issues/675

Can anyone confirm whether or not backup import works correctly on Mac GUI or Linux command line? I suspect the problem is only on Windows.

[Gentso1]

All good here, still have to end process to get setup to close, but everything else was smooth as silk

I just noticed if you don't check the Run box in the last screen of the setup wizard it exists. It must be launching the client as a child process or something. When you exit the client it exits setup if you had clicked Run.

That makes sense, thanks for the info.

[jakub]

Not sure if this has been fixed in 4.7 but in 4.5 when exporting the wallet and then trying to import it back I got this error:

[vikram]

0.4.5 and 0.4.6 are affected by this bug. Users should upgrade to 0.4.7 and restore any missing transactions by running:

Code Select Expand


rescan 274524

When 0.4.8 is released, it will restore these transactions automatically.

Users who did not keep their wallet synced before upgrading to 0.4.5+ may need to do a full rescan (warning: this could take a long time) to restore previous missing transactions:

Code Select Expand


rescan


[vikram]

I know this has been asked before but I can't find it. What flag do I need to add so that I don't build the test cases?

make bitshares_toolkit

[Shentist]

0.4.7 is not working on my machine. 0.4.5 worked fine, but now can't start the wallet anymore. i just send the crash report, but nothing was said about it. can bytemaster confirm that the crashrepot is save to send?

sry, but i am a tech noob and can't read hex. i just need confirmation that the wallet.key is not included in the crashreport. so i just wait now or can i somehow install 0.4.5? just tried it to install over the directory, but the same error is coming.

[Riverhead]

I was just talking with Valentine about this today.  He plans to switch to a new table library for performance reasons and to solve the very issue you just described.

+5%  You guys are on it. I feel I have finally backed the right horse for once :).

[bytemaster]

I know you guys are working on much more serious stuff right now but for when things settle a bit: a GUI suggestion. On the Markets tab the Buy and Ask books have column headers that scroll with the list rather than staying at the top. Small thing but it's sort of annoying.


On the plus side I love how the new send-to account box drop down search filter works now. Much better!

I was just talking with Valentine about this today.  He plans to switch to a new table library for performance reasons and to solve the very issue you just described. 

[Riverhead]

I know you guys are working on much more serious stuff right now but for when things settle a bit: a GUI suggestion. On the Markets tab the Buy and Ask books have column headers that scroll with the list rather than staying at the top. Small thing but it's sort of annoying.


On the plus side I love how the new send-to account box drop down search filter works now. Much better!

[Riverhead]

All good here, still have to end process to get setup to close, but everything else was smooth as silk

I just noticed if you don't check the Run box in the last screen of the setup wizard it exists. It must be launching the client as a child process or something. When you exit the client it exits setup if you had clicked Run.

[Gentso1]

All good here, still have to end process to get setup to close, but everything else was smooth as silk

[bytemaster]

DACSunlimited, you should do better on the management of  production version release. it is not a good practice to release the product too often.

Yes.. in the ideal world they would simply release once a week or once per month with a nice stable update.    It is quite embarrassing actually.

There is a strong desire to get bugs fixed for people that are experiencing as soon as possible.   We are working to expand our unit test coverage so that we can detect regressions prior to release.   

With crypto-systems like this I think it isn't a good idea to release too quickly, but it is also not a good idea to delay release of critical bug fixes.   

[Riverhead]

Updated to 0.4.7 without issue.

[crazybit]

DACSunlimited, you should do better on the management of  production version release. it is not a good practice to release the product too often.

[Riverhead]

I know this has been asked before but I can't find it. What flag do I need to add so that I don't build the test cases?

[DACSunlimited]

It is a severe bug, new transactions received might cause the transaction history being cleared.

https://github.com/dacsunlimited/bitsharesx/releases/tag/0.4.7