Quote from: iHashFury on January 15, 2015, 01:21:53 PM
Archlinux x32 cli has the following build error but still runs stable.

Code Select Expand

tests/drltc_tests/fc_math/CMakeFiles/multest.dir/build.make:54: recipe for target 'tests/drltc_tests/fc_math/CMakeFiles/multest.dir/multest.cpp.o' failed
make[2]: *** [tests/drltc_tests/fc_math/CMakeFiles/multest.dir/multest.cpp.o] Error 1
CMakeFiles/Makefile2:2424: recipe for target 'tests/drltc_tests/fc_math/CMakeFiles/multest.dir/all' failed
make[1]: *** [tests/drltc_tests/fc_math/CMakeFiles/multest.dir/all] Error 2
Makefile:76: recipe for target 'all' failed
make: *** [all] Error 2

Archlinux x64 gui built with no errors and runs stable.

ArchLinux here too .. have you update the submodules? git submodule update?
GCC or clang?

let me know when i can update download .org section thx ...

Archlinux x32 cli has the following build error but still runs stable.

tests/drltc_tests/fc_math/CMakeFiles/multest.dir/build.make:54: recipe for target 'tests/drltc_tests/fc_math/CMakeFiles/multest.dir/multest.cpp.o' failed
make[2]: *** [tests/drltc_tests/fc_math/CMakeFiles/multest.dir/multest.cpp.o] Error 1
CMakeFiles/Makefile2:2424: recipe for target 'tests/drltc_tests/fc_math/CMakeFiles/multest.dir/all' failed
make[1]: *** [tests/drltc_tests/fc_math/CMakeFiles/multest.dir/all] Error 2
Makefile:76: recipe for target 'all' failed
make: *** [all] Error 2

Archlinux x64 gui built with no errors and runs stable.

Quote from: Princelucky on January 15, 2015, 05:17:16 AM
so far it looks like the same problems as the last release.  I can't get synced enough to broadcast.  the chain stalled out at 45 days left. over 2 gig memory usage.  high cpu consumption.  can't quit the program without a crash.  program unexpectedly quits without any messages.  various elements of the GUI freeze while others still work.

Try to go into the console and type 'getinfo'. The blockchain could still be syncing in the background even though the GUI shows you've frozen. If getinfo also shows you stuck on the same particular block, then you're probably on a fork and have to delete everything except your wallet folder in your appdata/roaming/bitshares folder (after back up!!), and then save and put in checkpoints.json from http://www.riverhead.org/checkpoints.json

If your computer is old you just have to wait a long time. You can check which block you're on with getinfo. After a couple of hours it should be synced and then the wallet will calm down and can run without destroying your computer.

Upgrading delegates:

Machine 1:
- no issues

Loading blockchain from: /home/delegate/.BitShares/chain
Loading config from file: /home/delegate/.BitShares/config.json
Using built-in blockchain checkpoints
Tracking Statistics: true
Initializing state from built-in genesis file
Please be patient, this will take several minutes...
Successfully replayed 1529123 blocks in 2841 seconds.                         
Blockchain size changed from 609MiB to 606MiB.


Machine 2:
- no issues

Loading blockchain from: /home/coin/.BitShares/chain
Loading config from file: /home/coin/.BitShares/config.json
Using built-in blockchain checkpoints
Tracking Statistics: true
Initializing state from built-in genesis file
Please be patient, this will take several minutes...
Successfully replayed 1529121 blocks in 4721 seconds.                         
Blockchain size changed from 608MiB to 610MiB.


Machine 3:
- all fine
Loading blockchain from: /home/delegate/.BitShares/chain
Loading config from file: /home/delegate/.BitShares/config.json
Using built-in blockchain checkpoints
Tracking Statistics: true
Initializing state from built-in genesis file
Please be patient, this will take several minutes...
Successfully replayed 1530075 blocks in 4671 seconds.
Blockchain size changed from 609MiB to 607MiB.
Starting JSON RPC server on port 9988
Starting HTTP JSON RPC server on port 19988
Attempting to map P2P port 0 with UPNP...


Quote from: xeroc on January 15, 2015, 10:05:31 AM

Quote from: emski on January 15, 2015, 09:50:00 AM
This is probably due to a delegate(s) running multiple instances.

Let us identify them and tell them once and for all that this update strategy HARMS the network .. it's a no-go!

Look at the forks...
What I see from a glance is delegateX.Xeldal .

Quote from: emski on January 15, 2015, 09:50:00 AM
This is probably due to a delegate(s) running multiple instances.

Let us identify them and tell them once and for all that this update strategy HARMS the network .. it's a no-go!

Quote from: liondani on January 15, 2015, 09:00:48 AM
what about the 104 forks the last 24 hours?
Normally we are max at 10/24h
http://www.bitsharesblocks.com/home

I can understand it grows on update periods... but 104?  ???

This is probably due to a delegate(s) running multiple instances.

Quote from: Troglodactyl on January 15, 2015, 05:46:59 AM
The open margin orders list shows my call prices at 2x the feed price at entry, while the help text seems to indicate it should be 1.5x.

It has been 2x for quite a while now, this is not caused by the current version update.

Don't get crazy with the updates guys/delegates !!! We have plenty of time until the hard fork!!! Let's make it smoother this time!

what about the 104 forks the last 24 hours?
Normally we are max at 10/24h
http://www.bitsharesblocks.com/home

I can understand it grows on update periods... but 104?  ???

Ubuntu 14.04 Server
8GB ram
Looks fine.

All working fine here to windows 8.

Forgot that the fork hadn't kicked in yet and tried to import the vesting balances.
Got this error:

Quote10 assert_exception: Assert Exception
eval_state._current_state->get_head_block_num() >= DVS_V0_5_0_FORK_BLOCK_NUM

Not sure if this is a problem, but should the DVS be in this line?

Quote from: merlin0113 on January 15, 2015, 05:35:24 AM
All fine with me. OS: WIN 7 64bit

All fine as well.

Win7 64bit with 8GB RAM, non-SSD

All OK so far.

Installed successfully by overwriting the v0.4.27.2 installation.

First start with bitshares_client.exe, the blockchain replayed successfully. Synced.

Initializing state from built-in genesis file
Please be patient, this will take several minutes...
Successfully replayed 1528477 blocks in 2227 seconds.
Blockchain size changed from 605MiB to 611MiB.


Quit the command_line window and started the GUI with no problem.

It seems that the new GUI is faster than the previous version.