0.4.11 Testers Wanted (not mandatory)

[vikram]

RC2 testing: https://bitsharestalk.org/index.php?topic=8211.msg107598#msg107598

[xeroc]

@modprobe: welcome to the forum ... nice to have you here!

 

nice to have active delegates like nathan 

s/delegates/developers/
 

[liondani]

@modprobe: welcome to the forum ... nice to have you here!

 

nice to have active delegates like nathan 

[xeroc]

maybe,we could build the system on the "docker".this will reduce lots of bugs.

I maintain Docker images of BitSharesX. These are available at https://hub.docker.com/u/nathanhourt/ Note that nathanhourt/bitsharesx is probably the most interesting to others, but I also have an image which is preconfigured to run a chain server here.

Could some other dev please confirm that 'modprobe' is nathan?

Confirmed.

Nice ...

@modprobe: welcome to the forum ... nice to have you here!

[bytemaster]

maybe,we could build the system on the "docker".this will reduce lots of bugs.

I maintain Docker images of BitSharesX. These are available at https://hub.docker.com/u/nathanhourt/ Note that nathanhourt/bitsharesx is probably the most interesting to others, but I also have an image which is preconfigured to run a chain server here.

Could some other dev please confirm that 'modprobe' is nathan?

Confirmed.

[xeroc]

maybe,we could build the system on the "docker".this will reduce lots of bugs.

I maintain Docker images of BitSharesX. These are available at https://hub.docker.com/u/nathanhourt/ Note that nathanhourt/bitsharesx is probably the most interesting to others, but I also have an image which is preconfigured to run a chain server here.

Could some other dev please confirm that 'modprobe' is nathan?

[Riverhead]

Updated my old Thinkpad Core2Duo laptop with RC1. Before it was crashing a few times while it churned through the blockchain transaction scan but this time smooth as butter. The chain updated quickly but the transaction scanning is taking forever. Not a fault of the client, just a slow ass machine. So far zero stability issues with any RC1 client on any of my machines in any environment.

[modprobe]

maybe,we could build the system on the "docker".this will reduce lots of bugs.

I maintain Docker images of BitSharesX. These are available at https://hub.docker.com/u/nathanhourt/ Note that nathanhourt/bitsharesx is probably the most interesting to others, but I also have an image which is preconfigured to run a chain server here.

[Riverhead]

I left my Linux GUI on over night (Idle for about six hours) and it was fine this morning. Other than some cosmetic issues this release has mostly been flawless.


Only Issue: Sometimes the title bar menus (File Account) disappear and I can't exit the client. I've tried stop, exit, etc. from the console but they do not work. When I go out to a shell and kill the process it reports a seg fault. I'll see if I can reproduce running in gdb.

[xeroc]

Looks good so far... this is the first version that hasn't crashed on me soon after starting, and it's been running for hours now. :-)

yeeeeeha

As promised ... devs are fixing the crashing issues

[pc]

Looks good so far... this is the first version that hasn't crashed on me soon after starting, and it's been running for hours now. :-)

[huzhuzhu]

 

supporting and will try it on my local pc

[tonyk]

Anyone else have this issue with the Linux GUI? Doesn't do it in the 0.4.10 Windows binary. I have only built the gui on Ubuntu. Notice the LARGE amount of white space between the graph and the order fields.

Yes, but I think on Linux it has larger spaces between fields than Windows  in 0.4.10 too.

[Riverhead]

Anyone else have this issue with the Linux GUI? Doesn't do it in the 0.4.10 Windows binary. I have only built the gui on Ubuntu. Notice the LARGE amount of white space between the graph and the order fields.

[xeroc]

I also noticed another nice addition: 30 retries to bind the httpd port when you launch with --server. This is excellent cause I would often need to open then kill then restart the client in order to get it to bind to the correct port. Good job devs!

Yhea .. I was wondering about that too .. nice to see it fixed ..

[svk]

Runs stable for me (for the last 10 hours or so), lots of connections (160, although set to 20 desired, not that it matters really, the more the better ) and uses half the memory of 0.4.10!

Your comments about memory usage made switch over the bitsharesblocks client, as it was using almost 1gig of memory. With the new version from master it uses 500-600mb less than before, which is awesome!

I also noticed another nice addition: 30 retries to bind the httpd port when you launch with --server. This is excellent cause I would often need to open then kill then restart the client in order to get it to bind to the correct port. Good job devs!

[svk]

Running fine on my seednode as well, no crashes so far, have around 105 connections.

[wackou]

Runs stable for me (for the last 10 hours or so), lots of connections (160, although set to 20 desired, not that it matters really, the more the better ) and uses half the memory of 0.4.10!

[CoinHoarder]

fwiw 0.4.10 has been rock solid for me (linux cli build). 48 hours plus of no crashes.. about 24 hours longer than I've made it thus far.

The windows client is still pretty unstable though.

[puppies]

My seed node is up and running in gdb.  Currently with 140 connections.  I plan to run it overnight to see if it crashes with default settings.  If not I will increase maximum connections to 500 to give it a stress test.  If some other form of testing would be more advantageous, please advise.

[valzav]

Not really related to this testing but something I just noticed: I think the logic for choosing which delegate feed is expired in the gui might not be correct. I believe feeds should expire in 24 hours, but some feeds are red which are less than 24 hours old. It seems to be the feeds which were the previous day calendar day, not < 24 hours (unless we are now on a 12 hour cycle, in which case I need to change my script to make sure it updates at least every 12 hours).

Thank you. This bug is fixed https://github.com/BitShares/web_wallet/commit/a0dcce95798e8b7b2533e16d0299b81b5e3dc882

[emski]

Looks stable so far.
I'll update delegates and seed node.

I've updated my seed/chain but not my Delegate. Are we supposed to? I've been waiting for a post to this thread:

https://bitsharestalk.org/index.php?topic=7067.0

As it was written it is not mandatory. However it is better if someone tests this before release.

[Riverhead]

Looks stable so far.
I'll update delegates and seed node.

I've updated my seed/chain but not my Delegate. Are we supposed to? I've been waiting for a post to this thread:


https://bitsharestalk.org/index.php?topic=7067.0

[tonyk]

I'm testing the same one. I cloned it twice to be sure since the get_info says 0.4.10 but the tool_kit revision has a very new age.



{
  "bitshares_toolkit_revision": "b43f6c3871b9b8680996a8955dcf4a41facd563c",
  "bitshares_toolkit_revision_age": "9 hours ago",
  "fc_revision": "3222dc7c0be62b9ad0fdfd303c5c4f53b39063e6",
  "fc_revision_age": "4 days ago",
  "compile_date": "compiled on Sep  1 2014 at 12:52:49"
}

Thanks. I am not that stupid after all.
I will erase the scratched text above then...the sad thing is I just  found/recovered all my balances, saved and then  made some decent trades...and I cannot enjoy them... at least for a while...

[Riverhead]

I'm testing the same one. I cloned it twice to be sure since the get_info says 0.4.10 but the tool_kit revision has a very new age.



{
  "bitshares_toolkit_revision": "b43f6c3871b9b8680996a8955dcf4a41facd563c",
  "bitshares_toolkit_revision_age": "9 hours ago",
  "fc_revision": "3222dc7c0be62b9ad0fdfd303c5c4f53b39063e6",
  "fc_revision_age": "4 days ago",
  "compile_date": "compiled on Sep  1 2014 at 12:52:49"
}

[tonyk]

Forgot to post.
Clean build it on Ubuntu 14.10. Did not want to sync (gave it like 10 min with 7 connections).
So, copied the old database directory and now seem to work fine.
(Not-fillable shorts are not removed from the GUI of course...   )

I am an idiot....

Is this what I should be testing?

Code: [Select]

{
  "bitshares_toolkit_revision": "b43f6c3871b9b8680996a8955dcf4a41facd563c",
  "bitshares_toolkit_revision_age": "7 hours ago",
  "fc_revision": "3222dc7c0be62b9ad0fdfd303c5c4f53b39063e6",
  "fc_revision_age": "4 days ago",
  "compile_date": "compiled on Sep  1 2014 at 15:13:05"
}
Not that anybody told me if the above is 0.4.10 or 0.4.11 but it stated crashing on me after several orders in the market. Now it just closes itself after log in.

Not that anybody told me if the above is 0.4.10 or 0.4.11 but it stated crashing on me after several orders in the market. Now it just closes itself after log in.

[alt]

I just compiled & ran latest master. I am still seeing a short at 28.5714, which is below the current avg price of 30.9751.

There is a median price feed that overrules the average.

but the median price is about 34...
the filter seems work with command line,  not work with GUI

[chono]

maybe,we could build the system on the "docker".this will reduce lots of bugs.

来自我的 HTC 802d 上的 Tapatalk

[bitcoinerS]

GUI wallet error trying to add favorite

Code: [Select]

RPC Server Error: In method 'wallet_add_contact_account': Assert Exception (10)


Code: [Select]

>>> get_info
{
  "blockchain_head_block_num": 375910,
  "blockchain_head_block_age": "7 seconds old",
  "blockchain_head_block_timestamp": "2014-09-01T23:38:40",
  "blockchain_average_delegate_participation": "100.00 %",
  "blockchain_confirmation_requirement": 1,
  "blockchain_accumulated_fees": "256,062.98647 BTSX",
  "blockchain_delegate_pay_rate": "2.11692 BTSX",
  "blockchain_share_supply": "1,999,919,942.21843 BTSX",
  "blockchain_blocks_left_in_round": 12,
  "blockchain_next_round_time": "at least 2 minutes in the future",
  "blockchain_next_round_timestamp": "2014-09-01T23:40:40",
  "blockchain_random_seed": "ca375209443ba0f9041039a55d7056b6b6dcd6a1",
  "client_data_dir": "/home/slava/.BitSharesX",
  "client_version": "0.4.10",
  "network_num_connections": 5,
  "network_num_connections_max": 200,
  "ntp_time": "2014-09-01T23:38:47",
  "ntp_time_error": -0.111175,
  "wallet_open": true,
  "wallet_unlocked": true,
  "wallet_unlocked_until": "31 years  in the future",
  "wallet_unlocked_until_timestamp": "1910-04-04T18:56:51",
  "wallet_last_scanned_block_timestamp": "2014-09-01T23:38:40",
  "wallet_scan_progress": "100.00 %",
  "wallet_block_production_enabled": false,
  "wallet_next_block_production_time": null,
  "wallet_next_block_production_timestamp": null
}
default (unlocked) >>> about
{
  "bitshares_toolkit_revision": "b43f6c3871b9b8680996a8955dcf4a41facd563c",
  "bitshares_toolkit_revision_age": "7 hours ago",
  "fc_revision": "3222dc7c0be62b9ad0fdfd303c5c4f53b39063e6",
  "fc_revision_age": "4 days ago",
  "compile_date": "compiled on Sep  1 2014 at 16:31:10"
}



[tonyk]

Forgot to post.
Clean build it on Ubuntu 14.10. Did not want to sync (gave it like 10 min with 7 connections).
So, copied the old database directory and now seem to work fine.
(Not-fillable shorts are not removed from the GUI of course...   )

I am an idiot....

Is this what I should be testing?

Code: [Select]

{
  "bitshares_toolkit_revision": "b43f6c3871b9b8680996a8955dcf4a41facd563c",
  "bitshares_toolkit_revision_age": "7 hours ago",
  "fc_revision": "3222dc7c0be62b9ad0fdfd303c5c4f53b39063e6",
  "fc_revision_age": "4 days ago",
  "compile_date": "compiled on Sep  1 2014 at 15:13:05"
}
Not that anybody told me if the above is 0.4.10 or 0.4.11 but it stated crashing on me after several orders in the market. Now it just closes itself after log in.

[speedy]

no changes to gui since 4.10 so far. to rebuild the gui you need to delete the htdocs then rebuild the web_wallet

Code: [Select]

$ rm -r programs/qt_wallet/htdocs
$ make buildweb

Or you can just do this:
make forcebuildweb

[emski]

Looks stable so far.
I'll update delegates and seed node.

[tonyk]

Did somebody try the GUI?
If even a marginal improvements I will update my Linux to it
...not too many  bitBTC buyers anyway...so I as well might help the system that way, instead of trying to help start the bitBTC market.

[EDIT]
Please, I am newbie, can somebody post all the folders I gave to delete to have a fresh install in Ubuntu. Thanks.

no changes to gui since 4.10 so far. to rebuild the gui you need to delete the htdocs then rebuild the web_wallet

Code: [Select]

$ rm -r programs/qt_wallet/htdocs
$ make buildweb

Thanks for the code!

It should have at least the below, even though I got used to seeing not-fillable orders. What would be nice (and should be as easy as pie to change the '1h Avg. Price' to 'median price feed'), is seeing the median price feed without going to the console....

0.4.11 testing is now open and has some critical networking updates in it.   

3) Market Order Book now filters out over-priced shorts.

[maqifrnswa]

working fine so far, ubuntu 14.10

Not really related to this testing but something I just noticed: I think the logic for choosing which delegate feed is expired in the gui might not be correct. I believe feeds should expire in 24 hours, but some feeds are red which are less than 24 hours old. It seems to be the feeds which were the previous day calendar day, not < 24 hours (unless we are now on a 12 hour cycle, in which case I need to change my script to make sure it updates at least every 12 hours).

[maqifrnswa]

Did somebody try the GUI?
If even a marginal improvements I will update my Linux to it
...not too many  bitBTC buyers anyway...so I as well might help the system that way, instead of trying to help start the bitBTC market.

[EDIT]
Please, I am newbie, can somebody post all the folders I gave to delete to have a fresh install in Ubuntu. Thanks.

no changes to gui since 4.10 so far. to rebuild the gui you need to delete the htdocs then rebuild the web_wallet

Code: [Select]

$ make forcebuildweb
(thanks trader)

[tonyk]

Did somebody try the GUI?
If even a marginal improvements I will update my Linux to it
...not too many  bitBTC buyers anyway...so I as well might help the system that way, instead of trying to help start the bitBTC market.

[EDIT]
Please, I am newbie, can somebody post all the folders I gave to delete to have a fresh install in Ubuntu. Thanks.

[Riverhead]

Seed/chain node updated without issue to 0.4.11.


the info in the client still says 0.4.10 though...I'm guessing it just wasn't updated.

[king]

try...

[sfinder]

ok.will try on linux box

[theoretical]

this is publish too much...

People complain when there are too many bugs.  Then people complain when you make a new release to fix bugs.

The technology is fundamentally sound, and I'm confident that bugs will be worked out.  I think what's most important is holding off marketing efforts until things have settled down, otherwise the state of the client may hurt the coin's reputation.

[Xeldal]

I just compiled & ran latest master. I am still seeing a short at 28.5714, which is below the current avg price of 30.9751.

There is a median price feed that overrules the average.

Does the gui show the median price feed then? Also I still see overlapping on the bid/ask wall, which is confusing. Are you going to filter that in the future as well?

blockchain_get_feeds_for_asset USD
last entry MARKET shows "median_price": 0.0292277 USD/BTSX
or 34.214 BTSX/USD

[yinchanggong]

 
market need refined

[speedy]

I just compiled & ran latest master. I am still seeing a short at 28.5714, which is below the current avg price of 30.9751.

There is a median price feed that overrules the average.

Does the gui show the median price feed then? Also I still see overlapping on the bid/ask wall, which is confusing. Are you going to filter that in the future as well?

[bytemaster]

I just compiled & ran latest master. I am still seeing a short at 28.5714, which is below the current avg price of 30.9751.

There is a median price feed that overrules the average.

[ripplexiaoshan]

It's running on main chain or testing chain?

[speedy]

I just compiled & ran latest master. I am still seeing a short at 28.5714, which is below the current avg price of 30.9751.

[Riverhead]

Doesn't seem to be syncrhonizing at all.
Fresh data dir.
I have a lot of connections but it doesn't attempt to syncrhonize.

Update: Well it started now. For some reason it waited for a minute before starting sync

Is the directory updating? I found it shows "No connections" when using a chain server...

[Riverhead]

Building. Had to do a fresh clone.  git pull didn't do a new compile.  Oh well, probably good to refresh anyway . So far so good.

[emski]

Doesn't seem to be syncrhonizing at all.
Fresh data dir.
I have a lot of connections but it doesn't attempt to syncrhonize.

Update: Well it started now. For some reason it waited for a minute before starting sync

[x.ebit]

 

[bytemaster]

this is publish too much...

This is not a mandatory update.  This is not a 0.4.11 release... this is for testers only. 

[cgafeng]

this is publish too much...

[bytemaster]

0.4.11 testing is now open and has some critical networking updates in it.   

Please checkout the master branch.

https://github.com/dacsunlimited/bitsharesx

1) Resolves connect/disconnect bug
2) Improve networking performance
3) Market Order Book now filters out over-priced shorts.
4) Reduce some logging.

It is important for seed nodes to upgrade.
No hard forks (that we know of) for this release.

This update is NOT MANDATORY and this thread is only for those who would like to help in testing.