Author Topic: 0.4.11 Release Candidate 2 Testing  (Read 6524 times)

0 Members and 1 Guest are viewing this topic.

Offline tonyk

  • Hero Member
  • *****
  • Posts: 3308
    • View Profile
Re: 0.4.11 Release Candidate 2 Testing
« Reply #30 on: September 03, 2014, 09:43:33 pm »
upgraded to 0.4.11-rc2.
GUI
Win 7 /32 bit

Still hangs up in the first ever attempt to close the app.
This has been the case on Win and Ubuntu for the last 2-3 releases.


[RESOLVED in 0.4.12]!!!
The difference is that at least now with  0.4.11-rc2 , the force close, does not leave any btsx processes running.
« Last Edit: September 04, 2014, 07:39:56 pm by tonyk »
Lack of arbitrage is the problem, isn't it. And this 'should' solves it.

Offline Gentso1

  • Hero Member
  • *****
  • Posts: 931
    • View Profile
  • BitShares: gentso
Re: 0.4.11 Release Candidate 2 Testing
« Reply #31 on: September 03, 2014, 10:10:27 pm »
I have asked DAC Sun to produce a Windows 64 bit version.  The crypto is 2x faster in 64 bit.
I will give it a go when this happens

Offline tonyk

  • Hero Member
  • *****
  • Posts: 3308
    • View Profile
Re: 0.4.11 Release Candidate 2 Testing
« Reply #32 on: September 03, 2014, 10:17:22 pm »
First a question. Is the bitBTC:bitUSD going to have feed based median price?

If yes, it  now shows:

Median Price
31.1896
BitBTC/BitUSD
Lack of arbitrage is the problem, isn't it. And this 'should' solves it.

Offline bytemaster

Re: 0.4.11 Release Candidate 2 Testing
« Reply #33 on: September 03, 2014, 10:18:13 pm »
First a question. Is the bitBTC:bitUSD going to have feed based median price?

If yes, it  now shows:

Median Price
31.1896
BitBTC/BitUSD

No price feed for that pair, that is a GUI bug. 
For the latest updates checkout my blog: http://bytemaster.bitshares.org
Anything said on these forums does not constitute an intent to create a legal obligation or contract between myself and anyone else.   These are merely my opinions and I reserve the right to change them at any time.

Offline speedy

  • Hero Member
  • *****
  • Posts: 1160
    • View Profile
  • BitShares: speedy
Re: 0.4.11 Release Candidate 2 Testing
« Reply #34 on: September 03, 2014, 10:40:48 pm »
Im on RC2 and it shows the median at the top which is nice. Still would be even better to show it on the graph as well.

The overlapping has now stopped, I cant figure out if that is because of the new median-limit rule, or if its because the demand for BitUSD has increased.

Offline luckybit

  • Hero Member
  • *****
  • Posts: 2921
    • View Profile
  • BitShares: Luckybit
Re: 0.4.11 Release Candidate 2 Testing
« Reply #35 on: September 03, 2014, 11:13:23 pm »
0.4.11 release candidate has been posted to master at https://github.com/dacsunlimited/bitsharesx.git

https://github.com/dacsunlimited/bitsharesx/releases/tag/0.4.11-RC1


More market fixes so RC1 users still will have to upgrade:
https://github.com/dacsunlimited/bitsharesx/releases/tag/0.4.11-RC2

Changes in this update:
1) Major bugs fixes in the GUI
2) Shorts can sell at up to 10% below the peg *if* there are offers to buy above the peg.  The difference is captured as fees, gives priority to shorts willing to pay the highest fee.
3) Enhancements for canceling orders when managing a wallet imported from backup.
4) Deterministic key generation is now done on a per-account basis rather than per-wallet.  This should help place orders in the proper account when recovering from backups.
5) Average price gets set to the "median feed"
6) Major network bug fixes.

All hard-fork changes are currently scheduled to go into effect Friday at Noon. 

Test GUIs should be provided by DAC Sun Limited soon.

Still needs work. Transaction scanning seems to be stuck at 0% progress. Still unable to recover lost balances, but it isn't crashing anymore at least.
https://metaexchange.info | Bitcoin<->Altcoin exchange | Instant | Safe | Low spreads

Offline liondani

  • Hero Member
  • *****
  • Posts: 3737
  • Inch by inch, play by play
    • View Profile
    • My detailed info
  • BitShares: liondani
  • GitHub: liondani
Re: 0.4.11 Release Candidate 2 Testing
« Reply #36 on: September 03, 2014, 11:22:49 pm »
0.4.11 release candidate has been posted to master at https://github.com/dacsunlimited/bitsharesx.git

https://github.com/dacsunlimited/bitsharesx/releases/tag/0.4.11-RC1


More market fixes so RC1 users still will have to upgrade:
https://github.com/dacsunlimited/bitsharesx/releases/tag/0.4.11-RC2

Changes in this update:
1) Major bugs fixes in the GUI
2) Shorts can sell at up to 10% below the peg *if* there are offers to buy above the peg.  The difference is captured as fees, gives priority to shorts willing to pay the highest fee.
3) Enhancements for canceling orders when managing a wallet imported from backup.
4) Deterministic key generation is now done on a per-account basis rather than per-wallet.  This should help place orders in the proper account when recovering from backups.
5) Average price gets set to the "median feed"
6) Major network bug fixes.

All hard-fork changes are currently scheduled to go into effect Friday at Noon. 

Test GUIs should be provided by DAC Sun Limited soon.

Still needs work. Transaction scanning seems to be stuck at 0% progress. Still unable to recover lost balances, but it isn't crashing anymore at least.

same with me...
Because of this I deleted all folders except "wallets" and I am syncing from start again... 
right now at   "Last block was synced 20d 15h 42m 26s ago"  ...

When syncing is complete I will make a "wallet_rescan_blockchain" to see what happens....

Offline emski

  • Hero Member
  • *****
  • Posts: 1282
    • View Profile
    • http://lnkd.in/nPbhxG
Re: 0.4.11 Release Candidate 2 Testing
« Reply #37 on: September 03, 2014, 11:23:25 pm »
Looks this version works as expected.

I'll just post what I observed:

Just after I started the client I got 8 connections.
About 10 seconds after that connections dropped to 1.
I did not receive 2 blocks on time (392804 and 392805) and my delegate block production slot was just in that timeframe (392806). That resulted in a fork as my delegate knew only for 392803 at that particular moment.
Next delegate however decided to mine sign blocks on the right chain (previous 392804 and 392805). At that moment my delegate was showing: previous 2 blocks as missed (392804 and 392805), my block (392806), and the next block(392807) didn't show up at all (as it was sequential to 392805 which appears missed on my end). It was right after receiving 2 blocks on the right chain (after mine) when my delegate resynchronized and started to display its slot as missed. At the seed node however my delegate's block was marked missed on arrival as the seed node knew about the previous two blocks (392805 and 392804).
This looks like perfectly correct behavior to me (except dropped connections).
After that my delegate's connections got back to normal (20+) and everything run smoothly.

Here are the blocks in question:
Code: [Select]
392808  2014-09-03T22:38:00 www2.minebitshares-com          0       166     0.00000 BTSX    23      0.000833
392807  2014-09-03T22:37:50 delegate.bitder                 0       166     0.00000 BTSX    33      0.000775
392806  2014-09-03T22:37:40 dac.bts500                      0       166     0.00000 BTSX    43      0.003128
MISSED  2014-09-03T22:37:30 lotto-delegate                  N/A     N/A     N/A             N/A     N/A
392805  2014-09-03T22:37:20 delegate2.xeldal                1       424     0.10000 BTSX    63      0.005878
392804  2014-09-03T22:37:10 delegate.liondani               0       166     0.00000 BTSX    73      0.000258
392803  2014-09-03T22:37:00 daslab                          0       166     0.00000 BTSX    2       0.012986
392802  2014-09-03T22:36:50 delegate3.xeldal                1       424     0.10000 BTSX    2       0.003205


   FORKED BLOCK              FORKING BLOCK ID              SIGNING DELEGATE      TXN COUNT      SIZE           TIMESTAMP   LATENCY   VALID    IN CURRENT CHAIN
--------------------------------------------------------------------------------------------------------------------------------------------------------------
         392803
     7fa067f0d776c5d8f1372e0a5ca4a9c997d62523                lotto-delegate              0       166 2014-09-03T22:37:30         0     YES                  NO
     56b7877893610ff3353ec7435596fe3c2add8583             delegate.liondani              0       166 2014-09-03T22:37:10        73     YES                 YES

And a note for the future - "When updating you should make sure your updated delegate has enough connections before turning on block production (and simultaneously turning off the old delegate)".

PS: Not sure if this will be helpful for anyone as it was just me explaining to myself what happened. However I lost too much time to write it down and I'll post it anyway
« Last Edit: September 03, 2014, 11:29:20 pm by emski »

Offline gyhy

  • Hero Member
  • *****
  • Posts: 852
    • View Profile
Re: 0.4.11 Release Candidate 2 Testing
« Reply #38 on: September 03, 2014, 11:45:24 pm »
updating

Offline sfinder

  • Hero Member
  • *****
  • Posts: 1205
  • 4 Cores CPU+100GB SSD+anti-DDoS Pro
    • View Profile
Re: 0.4.11 Release Candidate 2 Testing
« Reply #39 on: September 03, 2014, 11:46:30 pm »
updating to RC2

help.chinese
chinese
微博:星在飘我在找|BTS X 受托人delegate ID:baidu
中国教育书店合作将20%收入捐献给贫困山区学生。
Cooperating with China Education Bookstore and will donate 20% of delegate income to the poor students

Offline bytemaster

Re: 0.4.11 Release Candidate Testing
« Reply #40 on: September 03, 2014, 11:54:45 pm »
This segfault occurs when quitting the GUI (after it has been open for a while).

Code: [Select]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Core was generated by `./BitSharesX'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x0000000000aadcfa in boost::asio::detail::task_io_service::post_immediate_completion (this=0x18, [email protected]=0x7ff070596450,
    [email protected]=false) at /usr/include/boost/asio/detail/impl/task_io_service.ipp:264
264   if (one_thread_ || is_continuation)
(gdb) bt
#0  0x0000000000aadcfa in boost::asio::detail::task_io_service::post_immediate_completion (this=0x18, [email protected]=0x7ff070596450,
    [email protected]=false) at /usr/include/boost/asio/detail/impl/task_io_service.ipp:264
#1  0x0000000000aadf00 in boost::asio::detail::epoll_reactor::start_op (this=0x7ff070027380, [email protected]=1, descriptor=155,
    [email protected]: 0x7ff04c001250, op=0x7ff070596450, is_continuation=<optimized out>, allow_speculative=true)
    at /usr/include/boost/asio/detail/impl/epoll_reactor.ipp:253
#2  0x0000000000aaf268 in boost::asio::detail::reactive_socket_service_base::start_op (this=0x7ff07045d168, impl=..., op_type=1, op=<optimized out>,
    is_continuation=<optimized out>, is_non_blocking=<optimized out>, noop=false) at /usr/include/boost/asio/detail/impl/reactive_socket_service_base.ipp:214
#3  0x0000000000ab2256 in async_send<boost::asio::const_buffers_1, boost::_bi::bind_t<void, void (*)(fc::shared_ptr<fc::promise<unsigned long> > const&, boost::system::error_code const&, unsigned long), boost::_bi::list3<boost::_bi::value<fc::shared_ptr<fc::promise<unsigned long> > >, boost::arg<1>, boost::arg<2> > > > (handler=...,
    flags=0, buffers=..., impl=..., this=0x7ff07045d168) at /usr/include/boost/asio/detail/reactive_socket_service_base.hpp:216
#4  async_send<boost::asio::const_buffers_1, boost::_bi::bind_t<void, void (*)(fc::shared_ptr<fc::promise<unsigned long> > const&, boost::system::error_code const&, unsigned long), boost::_bi::list3<boost::_bi::value<fc::shared_ptr<fc::promise<unsigned long> > >, boost::arg<1>, boost::arg<2> > > > (
    handler=<unknown type in /redacted/bitsharesx/programs/qt_wallet/bin/BitSharesX, CU 0x30d2e56, DIE 0x31418e3>, flags=0, buffers=..., impl=...,
    this=0x7ff07045d140) at /usr/include/boost/asio/stream_socket_service.hpp:330
#5  async_write_some<boost::asio::const_buffers_1, boost::_bi::bind_t<void, void (*)(fc::shared_ptr<fc::promise<unsigned long> > const&, boost::system::error_code const&, unsigned long), boost::_bi::list3<boost::_bi::value<fc::shared_ptr<fc::promise<unsigned long> > >, boost::arg<1>, boost::arg<2> > > > (
    handler=<unknown type in /redacted/bitsharesx/programs/qt_wallet/bin/BitSharesX, CU 0x30d2e56, DIE 0x3115ea8>, buffers=..., this=0x7ff07048fef8)
    at /usr/include/boost/asio/basic_stream_socket.hpp:732
#6  fc::asio::write_some<boost::asio::basic_stream_socket<boost::asio::ip::tcp, boost::asio::stream_socket_service<boost::asio::ip::tcp> >, boost::asio::const_buffers_1>
    (s=..., buf=...) at /redacted/bitsharesx/libraries/fc/include/fc/asio.hpp:122
#7  0x0000000000db0399 in fc::detail::rate_limiting_group_impl::writesome (this=0x7ff070433770, socket=...,
    buffer=0x7ff049e6d7a0 "\337\362n\342\360\274\v\005\065\366LJ", length=16) at /redacted/bitsharesx/libraries/fc/src/network/rate_limiting.cpp:249
#8  0x0000000000a5ccc7 in fc::ostream::write ([email protected]=0x7ff07048fed8, [email protected]=0x7ff049e6d7a0 "\337\362n\342\360\274\v\005\065\366LJ", len=16)
    at /redacted/bitsharesx/libraries/fc/src/io/iostream.cpp:365
#9  0x0000000000be22ae in bts::net::stcp_socket::writesome (this=0x7ff07048fe80, buffer=0x7ff070001fb0 "\b", len=<optimized out>)
    at /redacted/bitsharesx/libraries/net/stcp_socket.cpp:93
#10 0x0000000000a5ccc7 in fc::ostream::write ([email protected]=0x7ff07048fe80, [email protected]=0x7ff070001fb0 "\b", [email protected]=16)
    at /redacted/bitsharesx/libraries/fc/src/io/iostream.cpp:365
#11 0x0000000000bc30d0 in bts::net::detail::message_oriented_connection_impl::send_message (this=0x7ff07048fe70, message_to_send=...)
    at /redacted/bitsharesx/libraries/net/message_oriented_connection.cpp:251
#12 0x0000000000bc3bb8 in bts::net::message_oriented_connection::send_message ([email protected]=0x7ff070465af8, message_to_send=...)
    at /redacted/bitsharesx/libraries/net/message_oriented_connection.cpp:328
#13 0x0000000000bbda96 in bts::net::peer_connection::send_queued_messages_task (this=0x7ff070465a90)
    at /redacted/bitsharesx/libraries/net/peer_connection.cpp:236
#14 0x0000000000bbf5dc in operator() (__closure=<optimized out>) at /redacted/bitsharesx/libraries/net/peer_connection.cpp:301
#15 fc::detail::void_functor_run<bts::net::peer_connection::send_message(const bts::net::message&)::<lambda()> >::run(void *, void *) (functor=<optimized out>,
    prom=0x7ff070466660) at /redacted/bitsharesx/libraries/fc/include/fc/thread/task.hpp:83
#16 0x0000000000a4e115 in fc::task_base::run_impl (this=0x7ff070466670) at /redacted/bitsharesx/libraries/fc/src/thread/task.cpp:43
#17 0x0000000000a4cbb3 in run_next_task (this=<optimized out>) at /redacted/bitsharesx/libraries/fc/src/thread/thread_d.hpp:398
#18 fc::thread_d::process_tasks (this=0x7ff0700008c0) at /redacted/bitsharesx/libraries/fc/src/thread/thread_d.hpp:422
#19 0x0000000000a4ce21 in fc::thread_d::start_process_tasks (my=140670647929024) at /redacted/bitsharesx/libraries/fc/src/thread/thread_d.hpp:378
#20 0x0000000000deedee in make_fcontext ()
#21 0x00007ff0700008c0 in ?? ()
#22 0x0000000000000000 in ?? ()
Please let me know if you can repeat this error in further runs. Also, before you shut down, can you check how many connections and how much memory you are using? Are you just operating with default settings, or have you increased node count or anything like that?

Dan N. reports they have duplicated this crash and have a probable fix.    It will have to wait for 0.4.12.
For the latest updates checkout my blog: http://bytemaster.bitshares.org
Anything said on these forums does not constitute an intent to create a legal obligation or contract between myself and anyone else.   These are merely my opinions and I reserve the right to change them at any time.

Offline bytemaster

Re: 0.4.11 Release Candidate 2 Testing
« Reply #41 on: September 03, 2014, 11:56:08 pm »
Windows 64 bit version was just posted by DAC Sun Limited...

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


This version should be significantly faster than the 32 bit version, but may have new undiscovered crashes.  Please test.
For the latest updates checkout my blog: http://bytemaster.bitshares.org
Anything said on these forums does not constitute an intent to create a legal obligation or contract between myself and anyone else.   These are merely my opinions and I reserve the right to change them at any time.

Offline GaltReport

Re: 0.4.11 Release Candidate 2 Testing
« Reply #42 on: September 04, 2014, 12:08:23 am »
Windows 64 bit version was just posted by DAC Sun Limited...

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


This version should be significantly faster than the 32 bit version, but may have new undiscovered crashes.  Please test.

I get error: "The application was unable to start correctly..." for 64-bit version.
« Last Edit: September 04, 2014, 12:15:39 am by GaltReport »

38PTSWarrior

  • Guest
Re: 0.4.11 Release Candidate 2 Testing
« Reply #43 on: September 04, 2014, 12:11:25 am »
I run the exe in Wine and it feels much better now. The "check for updates" looks promising. The flickering between the windows also is gone. Props to the devs. Please keep bug fixing for Wine because of people like me with old hardware and Linux only, thaaaaaanks :)

Offline liondani

  • Hero Member
  • *****
  • Posts: 3737
  • Inch by inch, play by play
    • View Profile
    • My detailed info
  • BitShares: liondani
  • GitHub: liondani
Re: 0.4.11 Release Candidate 2 Testing
« Reply #44 on: September 04, 2014, 12:37:48 am »
I made 2 short orders on bitBTC/BTSX market and I can't cancel both of them !

Code: [Select]
TYPE PRICE (BTSX/BITBTC) QUANTITY (BITBTC) COST (BTSX) COLLATERAL (BTSX) ACTION
Short 15,500.00            1.00                 15,500.00                     canceling..
Short 15,800.00            1.00000000         15,799.99999             canceling..

RPC Server Error: In method 'wallet_market_cancel_order': unknown market order (20011)
« Last Edit: September 04, 2014, 12:39:44 am by liondani »