BitShares Forum
Main => General Discussion => Topic started by: bytemaster on September 09, 2014, 07:01:49 pm
-
https://github.com/dacsunlimited/bitsharesx/releases/tag/0.4.13-RC1
https://github.com/dacsunlimited/bitsharesx/releases/tag/v0.4.13
There are some major updates in this particular revision and it is once again mandatory with a hard fork scheduled in 24 hours (3 PM EST).
1) Fix short matching issue
2) Implement BitAsset Yield / Rewards / Interest
3) Groundwork for paying fees with BitAssets
I would recommend all delegates / seed nodes upgrade ASAP and publish your version.
-
on it ..
-
I've updated seed node and delegates.
Version is published.
-
btsx.chinesecommunity and btsx.xiaoshan updated +5%
-
riverhead-del-server-1 and chain/seed updated.
(http://i.imgur.com/I3FCIPN.png)
-
(http://www.quickmeme.com/img/10/10488e5a9007ecbcd353cd71acc98e4ba852c5cef384f08327c2a88a072e6cf2.jpg)
-
done
-
Win binary is coming soon I hope?!
Or am I better off switching to Linux?
-
Win binary is coming soon I hope?!
It's still Release candidate. Give them 12h 6h to find the last bugs :)
Or am I better off switching to Linux?
generally spoken?
//edit: ok .. i made that number up :)
-
Win binary is coming soon I hope?!
It's still Release candidate. Give them 12h 6h to find the last bugs :)
Or am I better off switching to Linux?
generally spoken?
//edit: ok .. i made that number up :)
My response is in and can you please answer in the 'Stupid question' thread.
-
Being a release candidate means that we expect it to be "release quality", but don't want everyone to jump on it yet until it has been in more hands.
Most issues tend to show up in short order. If something does happen then the hard fork can be delayed.
-
Being a release candidate means that we expect it to be "release quality", but don't want everyone to jump on it yet until it has been in more hands.
Most issues tend to show up in short order. If something does happen then the hard fork can be delayed.
Clean compile and blockchain synchronization works for me.
Delegates and seed node are stable so It is indeed release quality.
-
Done. No problems noticed so far.
I'm currently a standby delegate, vote me into active if possible. Thanks!
-
Are you using git clone and then checkout master or do you extract the tar.gz file and then terminal your way through? Could someone tell me the command please? Thanks
-
sun.delegate.service
moon.delegate.service
updated,and published version.
-
Are you using git clone and then checkout master or do you extract the tar.gz file and then terminal your way through? Could someone tell me the command please? Thanks
http://wiki.bitshares.org/index.php/BuildInstructionsBitSharesX
I use git-master .. not the 0.4.13-rc1 tag/label
-
may I remind delegates to publish their version after
backup upgrade. There is now a nice RPC call for that:
wallet_publish_version <publishing_account_name> [paying_account_name]
-
Do you mean: "git checkout master" when you say git-master?
I did git checkout master ad it say's I am on the same branch as origin/master.
Thinking for myself 1-2-3, should be alright?
Edit: I think thiss is not necessary anymore:
git submodule init
git submodule update
cmake .
make
Instead only
git submodule init
git submodule update
cd bitsharesx
cmake -DINCLUDE_QT_WALLET=ON .
rm -r programs/qt_wallet/htdocs # in the case you are updating an existing build
cd programs/web_wallet
sudo npm install -g lineman
npm install
cd -
make buildweb
make BitSharesX
-
Active delegates spartako,spartako1,spartako2 updated and published new version 0.4.13-RC1
-
may I remind delegates to publish their version after backup. There is now a nice RPC call for that:
wallet_publish_version <publishing_account_name> [paying_account_name]
What do you mean by "after backup" ?
-
Do you mean: "git checkout master" when you say git-master?
I did git checkout master ad it say's I am on the same branch as origin/master.
Thinking for myself 1-2-3, should be alright?
Edit: I think thiss is not necessary anymore:
git submodule init
git submodule update
cmake .
make
I just clone the repo (or do a "git pull" to update) .. no explicit checkout .. although recommended ..
Instead only
git submodule init
git submodule update
cd bitsharesx
cmake -DINCLUDE_QT_WALLET=ON .
rm -r programs/qt_wallet/htdocs # in the case you are updating an existing build
cd programs/web_wallet
sudo npm install -g lineman
npm install
cd -
make buildweb
make BitSharesX
-
What do you mean by "after backup" ?
typo .. fixed to "upgrade" ..sorry
-
wackou-delegate updated, everything running smooth so far +5%
-
Thanks!!
-
Are you using git clone and then checkout master or do you extract the tar.gz file and then terminal your way through? Could someone tell me the command please? Thanks
http://wiki.bitshares.org/index.php/BuildInstructionsBitSharesX
I use git-master .. not the 0.4.13-rc1 tag/label
I guess there are several ways to do it, but this worked for me:
git checkout 0.4.13RC1
-
Are you using git clone and then checkout master or do you extract the tar.gz file and then terminal your way through? Could someone tell me the command please? Thanks
http://wiki.bitshares.org/index.php/BuildInstructionsBitSharesX
I use git-master .. not the 0.4.13-rc1 tag/label
I guess there are several ways to do it, but this worked for me:
git checkout 0.4.13RC1
Is there any difference between checkout master and checkout 0.4.13RC1?
-
(http://robohash.org/set_1/delegate.liondani?size=75x75)delegate.liondani upgraded to 0.4.13
-
Are you using git clone and then checkout master or do you extract the tar.gz file and then terminal your way through? Could someone tell me the command please? Thanks
http://wiki.bitshares.org/index.php/BuildInstructionsBitSharesX
I use git-master .. not the 0.4.13-rc1 tag/label
I guess there are several ways to do it, but this worked for me:
git checkout 0.4.13RC1
Is there any difference between checkout master and checkout 0.4.13RC1?
Only some build fixes for latest boost and clang versions... no functional difference.
-
Market isn't loading in GUI. Is that because the fork hasn't happened yet?
-
Market was loading over here ..
-
Market isn't loading in GUI. Is that because the fork hasn't happened yet?
GUI loads for me.
-
(http://www.zimagez.com/full/18beed625724f87d817defaa1cf6b754bb3cab11ad67d62b6924c0fb25bf0a9da72665d1d65469386f3d6c694722b7c15eea9fe12e7fc68e.php)
-
(http://www.zimagez.com/full/18beed625724f87d817defaa1cf6b754bb3cab11ad67d62b6924c0fb25bf0a9da72665d1d65469386f3d6c694722b7c15eea9fe12e7fc68e.php)
OS? Did you build from master? Which market did you attempt to load?
-
Ubuntu 14.04. I am rebuilding on checkout master.
Update: Still no love under master. I tried updating the dependencies too. This is on a fresh clone.
Just clicked on the market tab. Hadn't gotten a list of markets yet.
-
delegate*.xeldal updated to 0.4.13-RC1
feeds updated
-
Done
-
Looks like I need a new picture hosting site. I'll mess with it more when back from dinner
-
Upgraded to 0.4.13-RC1:
delegate1-galt
delegate1.john-galt
0.4.13 Version Published.
-
Looks like I need a new picture hosting site. I'll mess with it more when back from dinner
Use imgur, it's the most popular one (and probably the most reliable)
-
Looks like I need a new picture hosting site. I'll mess with it more when back from dinner
Use imgur, it's the most popular one
I was till this thread...but zimagez had integration with screenshot app in Ubuntu..back to imgur
-
x.ebit
rose.ebit
upgraded.
bitrose<--->btsx market is up. +5% +5%
-
done.
-
updating
completed and updated version info
-
I updated it, but my short is missing from open orders. Any advice how to find it please :)
-
Updated to 0.4.13-RC1 on win 7/32 bit.
No obvious problems so far. Took about 40% more memory to initial index.
The annoying 'wrong auto complete' [you know when you click on the order from the order book, it auto populates your order] is still there though.
To make matters worse the graph (even though it is prettier now :) ) is still at its usual spot -between market bid/asks and the order entry field. This makes it hard to enter your orders, as it involves a lot of scrawling...
I have almost half a dollar in interest yield, seems too high of a number????
-
Tony k is a high roller
Sent from my SCH-I535 using Tapatalk
-
google.helloworld
microsoft.helloworld
done 8)
-
I updated it, but my short is missing from open orders. Any advice how to find it please :)
I've had the same thing. I deleted the 0.4.13 and went back to the 0.4.12. Just a little bug ^^
-
I have almost half a dollar in interest yield, seems too high of a number? ???
I believe he said it would be retroactive.
-
Updated to 0.4.13-RC1 on win 7/32 bit.
The GUI lost (not showing) my open orders!!!!! Newly placed - after upgrading!
ask and short order in market bitBTC!
-
Updated to 0.4.13-RC1 on win 7/32 bit.
The GUI lost (not showing) my open orders!!!!! Newly placed - after upgrading!
ask and short order in market bitBTC!
I can fix this tonight and dacsun can test out new gui hotfix push feature when they wake up
Sent from my SCH-I535 using Tapatalk
-
done
delegate.bitsuperlab
delegate-alt
delegate-baozi
delegate-watchman
-
Updated to 0.4.13-RC1 on win 7/32 bit.
The GUI lost (not showing) my open orders!!!!! Newly placed - after upgrading!
ask and short order in market bitBTC!
GUI isn't displaying my open orders for selling BTSX in the bitUSD market so my balances are also incorrect. I'm running 10.9.4
-
just FYI:
wallet_publish_version sets your version to 0.4.13, not 0.4.13-RC1
is there a preference which one you want to see?
-
Updated to 0.4.13-RC1 on win 7/32 bit.
The GUI lost (not showing) my open orders!!!!! Newly placed - after upgrading!
ask and short order in market bitBTC!
I can fix this tonight and dacsun can test out new gui hotfix push feature when they wake up
Sent from my SCH-I535 using Tapatalk
I do not know if it related to the other issue above (probably not) but
Cannot cancel the ask order! (managed to cancel the short)
>> wallet_market_cancel_order b91026170893374df40763a675c7537fe7812c37
4 parse_error_exception: Parse Error
Unexpected char '98' in "b91026170893374df40763a675c7537fe7812c37"
{"c":98,"s":"b91026170893374df40763a675c7537fe7812c37"}
bitshares json.cpp:411 fc::variant_from_stream
Error parsing argument 1 of command "wallet_market_cancel_order": [{"context":{"level":"error","file":"json.cpp","line":411,"method":"fc::variant_from_stream","hostname":"","thread_name":"bitshares","timestamp":"20140910T010559.851643"},"format":"Unexpected char '${c}' in \"${s}\"","data":{"c":98,"s":"b91026170893374df40763a675c7537fe7812c37"}}]
{"argument_number":1,"command":"wallet_market_cancel_order","detail":[{"context":{"level":"error","file":"json.cpp","line":411,"method":"fc::variant_from_stream","hostname":"","thread_name":"bitshares","timestamp":"20140910T010559.851643"},"format":"Unexpected char '${c}' in \"${s}\"","data":{"c":98,"s":"b91026170893374df40763a675c7537fe7812c37"}}]}
bitshares cli.cpp:497 bts::cli::detail::cli_impl::parse_argument_of_known_type
{"parameter_index":0}
bitshares cli.cpp:500 bts::cli::detail::cli_impl::parse_argument_of_known_type
Error parsing argument 1 of command "wallet_market_cancel_order": [{"context":{"level":"error","file":"json.cpp","line":411,"method":"fc::variant_from_stream","hostname":"","thread_name":"bitshares","timestamp":"20140910T010559.851643"},"format":"Unexpected char '${c}' in \"${s}\"","data":{"c":98,"s":"b91026170893374df40763a675c7537fe7812c37"}},{"context":{"level":"error","file":"cli.cpp","line":497,"method":"bts::cli::detail::cli_impl::parse_argument_of_known_type","hostname":"","thread_name":"bitshares","timestamp":"20140910T010559.851643"},"format":"Error parsing argument ${argument_number} of command \"${command}\": ${detail}","data":{"argument_number":1,"command":"wallet_market_cancel_order","detail":[{"context":{"level":"error","file":"json.cpp","line":411,"method":"fc::variant_from_stream","hostname":"","thread_name":"bitshares","timestamp":"20140910T010559.851643"},"format":"Unexpected char '${c}' in \"${s}\"","data":{"c":98,"s":"b91026170893374df40763a675c7537fe7812c37"}}]}},{"context":{"level":"warn","file":"cli.cpp","line":500,"method":"bts::cli::detail::cli_impl::parse_argument_of_known_type","hostname":"","thread_name":"bitshares","timestamp":"20140910T010559.851643"},"format":"","data":{"parameter_index":0}}]
{"argument_number":1,"command":"wallet_market_cancel_order","detail":[{"context":{"level":"error","file":"json.cpp","line":411,"method":"fc::variant_from_stream","hostname":"","thread_name":"bitshares","timestamp":"20140910T010559.851643"},"format":"Unexpected char '${c}' in \"${s}\"","data":{"c":98,"s":"b91026170893374df40763a675c7537fe7812c37"}},{"context":{"level":"error","file":"cli.cpp","line":497,"method":"bts::cli::detail::cli_impl::parse_argument_of_known_type","hostname":"","thread_name":"bitshares","timestamp":"20140910T010559.851643"},"format":"Error parsing argument ${argument_number} of command \"${command}\": ${detail}","data":{"argument_number":1,"command":"wallet_market_cancel_order","detail":[{"context":{"level":"error","file":"json.cpp","line":411,"method":"fc::variant_from_stream","hostname":"","thread_name":"bitshares","timestamp":"20140910T010559.851643"},"format":"Unexpected char '${c}' in \"${s}\"","data":{"c":98,"s":"b91026170893374df40763a675c7537fe7812c37"}}]}},{"context":{"level":"warn","file":"cli.cpp","line":500,"method":"bts::cli::detail::cli_impl::parse_argument_of_known_type","hostname":"","thread_name":"bitshares","timestamp":"20140910T010559.851643"},"format":"","data":{"parameter_index":0}}]}
bitshares cli.cpp:361 bts::cli::detail::cli_impl::parse_recognized_interactive_command
{}
bitshares cli.cpp:368 bts::cli::detail::cli_impl::parse_recognized_interactive_command
Error parsing command "wallet_market_cancel_order": Parse Error (4)
Unexpected char '98' in "b91026170893374df40763a675c7537fe7812c37"
Error parsing argument 1 of command "wallet_market_cancel_order": [{"context":{"level":"error","file":"json.cpp","line":411,"method":"fc::variant_from_stream","hostname":"","thread_name":"bitshares","timestamp":"20140910T010559.851643"},"format":"Unexpected char '${c}' in \"${s}\"","data":{"c":98,"s":"b91026170893374df40763a675c7537fe7812c37"}}]
Error parsing argument 1 of command "wallet_market_cancel_order": [{"context":{"level":"error","file":"json.cpp","line":411,"method":"fc::variant_from_stream","hostname":"","thread_name":"bitshares","timestamp":"20140910T010559.851643"},"format":"Unexpected char '${c}' in \"${s}\"","data":{"c":98,"s":"b91026170893374df40763a675c7537fe7812c37"}},{"context":{"level":"error","file":"cli.cpp","line":497,"method":"bts::cli::detail::cli_impl::parse_argument_of_known_type","hostname":"","thread_name":"bitshares","timestamp":"20140910T010559.851643"},"format":"Error parsing argument ${argument_number} of command \"${command}\": ${detail}","data":{"argument_number":1,"command":"wallet_market_cancel_order","detail":[{"context":{"level":"error","file":"json.cpp","line":411,"method":"fc::variant_from_stream","hostname":"","thread_name":"bitshares","timestamp":"20140910T010559.851643"},"format":"Unexpected char '${c}' in \"${s}\"","data":{"c":98,"s":"b91026170893374df40763a675c7537fe7812c37"}}]}},{"context":{"level":"warn","file":"cli.cpp","line":500,"method":"bts::cli::detail::cli_impl::parse_argument_of_known_type","hostname":"","thread_name":"bitshares","timestamp":"20140910T010559.851643"},"format":"","data":{"parameter_index":0}}]
Usage:
wallet_market_cancel_order <order_id> Cancel an order
Cancel an order
Parameters:
order_id (order_id, required): the ID of the order to cancel
Returns:
transaction_record
>> wallet_market_order_list BTC BTSX
TYPE QUANTITY PRICE BALANCE COST COLLATERAL ID
================================================================================================================================
cover_order 182,250.00000 BTSX 0.000027434842249657 BTC / BTSX5.00000000 BTC 4.99999999 BTC 243,000.00000 BTSX 2f7c01f9f56ff0d6286473ad0b68561b654ab0c0
cover_order 41,973.75000 BTSX 0.000027793561452098 BTC / BTSX1.16660000 BTC 1.16659999 BTC 55,965.00000 BTSX 8b41685adea121132b5546ebdd9dd054cc256aae
ask_order 27,393.75000 BTSX 0.000082135523613963 BTC / BTSX27,393.75000 BTSX 2.25000000 BTC N/A b91026170893374df40763a675c7537fe7812c37
Also did you change the format of the order ID? It is no longer BTSXxxxxxxxxxxxxxxxxxx...
-
Place the ID in quotes
Updated to 0.4.13-RC1 on win 7/32 bit.
The GUI lost (not showing) my open orders!!!!! Newly placed - after upgrading!
ask and short order in market bitBTC!
I can fix this tonight and dacsun can test out new gui hotfix push feature when they wake up
Sent from my SCH-I535 using Tapatalk
I do not know if it related to the other issue above (probably not) but
Cannot cancel the ask order! (managed to cancel the short)
>> wallet_market_cancel_order b91026170893374df40763a675c7537fe7812c37
4 parse_error_exception: Parse Error
Unexpected char '98' in "b91026170893374df40763a675c7537fe7812c37"
{"c":98,"s":"b91026170893374df40763a675c7537fe7812c37"}
bitshares json.cpp:411 fc::variant_from_stream
Error parsing argument 1 of command "wallet_market_cancel_order": [{"context":{"level":"error","file":"json.cpp","line":411,"method":"fc::variant_from_stream","hostname":"","thread_name":"bitshares","timestamp":"20140910T010559.851643"},"format":"Unexpected char '${c}' in \"${s}\"","data":{"c":98,"s":"b91026170893374df40763a675c7537fe7812c37"}}]
{"argument_number":1,"command":"wallet_market_cancel_order","detail":[{"context":{"level":"error","file":"json.cpp","line":411,"method":"fc::variant_from_stream","hostname":"","thread_name":"bitshares","timestamp":"20140910T010559.851643"},"format":"Unexpected char '${c}' in \"${s}\"","data":{"c":98,"s":"b91026170893374df40763a675c7537fe7812c37"}}]}
bitshares cli.cpp:497 bts::cli::detail::cli_impl::parse_argument_of_known_type
{"parameter_index":0}
bitshares cli.cpp:500 bts::cli::detail::cli_impl::parse_argument_of_known_type
Error parsing argument 1 of command "wallet_market_cancel_order": [{"context":{"level":"error","file":"json.cpp","line":411,"method":"fc::variant_from_stream","hostname":"","thread_name":"bitshares","timestamp":"20140910T010559.851643"},"format":"Unexpected char '${c}' in \"${s}\"","data":{"c":98,"s":"b91026170893374df40763a675c7537fe7812c37"}},{"context":{"level":"error","file":"cli.cpp","line":497,"method":"bts::cli::detail::cli_impl::parse_argument_of_known_type","hostname":"","thread_name":"bitshares","timestamp":"20140910T010559.851643"},"format":"Error parsing argument ${argument_number} of command \"${command}\": ${detail}","data":{"argument_number":1,"command":"wallet_market_cancel_order","detail":[{"context":{"level":"error","file":"json.cpp","line":411,"method":"fc::variant_from_stream","hostname":"","thread_name":"bitshares","timestamp":"20140910T010559.851643"},"format":"Unexpected char '${c}' in \"${s}\"","data":{"c":98,"s":"b91026170893374df40763a675c7537fe7812c37"}}]}},{"context":{"level":"warn","file":"cli.cpp","line":500,"method":"bts::cli::detail::cli_impl::parse_argument_of_known_type","hostname":"","thread_name":"bitshares","timestamp":"20140910T010559.851643"},"format":"","data":{"parameter_index":0}}]
{"argument_number":1,"command":"wallet_market_cancel_order","detail":[{"context":{"level":"error","file":"json.cpp","line":411,"method":"fc::variant_from_stream","hostname":"","thread_name":"bitshares","timestamp":"20140910T010559.851643"},"format":"Unexpected char '${c}' in \"${s}\"","data":{"c":98,"s":"b91026170893374df40763a675c7537fe7812c37"}},{"context":{"level":"error","file":"cli.cpp","line":497,"method":"bts::cli::detail::cli_impl::parse_argument_of_known_type","hostname":"","thread_name":"bitshares","timestamp":"20140910T010559.851643"},"format":"Error parsing argument ${argument_number} of command \"${command}\": ${detail}","data":{"argument_number":1,"command":"wallet_market_cancel_order","detail":[{"context":{"level":"error","file":"json.cpp","line":411,"method":"fc::variant_from_stream","hostname":"","thread_name":"bitshares","timestamp":"20140910T010559.851643"},"format":"Unexpected char '${c}' in \"${s}\"","data":{"c":98,"s":"b91026170893374df40763a675c7537fe7812c37"}}]}},{"context":{"level":"warn","file":"cli.cpp","line":500,"method":"bts::cli::detail::cli_impl::parse_argument_of_known_type","hostname":"","thread_name":"bitshares","timestamp":"20140910T010559.851643"},"format":"","data":{"parameter_index":0}}]}
bitshares cli.cpp:361 bts::cli::detail::cli_impl::parse_recognized_interactive_command
{}
bitshares cli.cpp:368 bts::cli::detail::cli_impl::parse_recognized_interactive_command
Error parsing command "wallet_market_cancel_order": Parse Error (4)
Unexpected char '98' in "b91026170893374df40763a675c7537fe7812c37"
Error parsing argument 1 of command "wallet_market_cancel_order": [{"context":{"level":"error","file":"json.cpp","line":411,"method":"fc::variant_from_stream","hostname":"","thread_name":"bitshares","timestamp":"20140910T010559.851643"},"format":"Unexpected char '${c}' in \"${s}\"","data":{"c":98,"s":"b91026170893374df40763a675c7537fe7812c37"}}]
Error parsing argument 1 of command "wallet_market_cancel_order": [{"context":{"level":"error","file":"json.cpp","line":411,"method":"fc::variant_from_stream","hostname":"","thread_name":"bitshares","timestamp":"20140910T010559.851643"},"format":"Unexpected char '${c}' in \"${s}\"","data":{"c":98,"s":"b91026170893374df40763a675c7537fe7812c37"}},{"context":{"level":"error","file":"cli.cpp","line":497,"method":"bts::cli::detail::cli_impl::parse_argument_of_known_type","hostname":"","thread_name":"bitshares","timestamp":"20140910T010559.851643"},"format":"Error parsing argument ${argument_number} of command \"${command}\": ${detail}","data":{"argument_number":1,"command":"wallet_market_cancel_order","detail":[{"context":{"level":"error","file":"json.cpp","line":411,"method":"fc::variant_from_stream","hostname":"","thread_name":"bitshares","timestamp":"20140910T010559.851643"},"format":"Unexpected char '${c}' in \"${s}\"","data":{"c":98,"s":"b91026170893374df40763a675c7537fe7812c37"}}]}},{"context":{"level":"warn","file":"cli.cpp","line":500,"method":"bts::cli::detail::cli_impl::parse_argument_of_known_type","hostname":"","thread_name":"bitshares","timestamp":"20140910T010559.851643"},"format":"","data":{"parameter_index":0}}]
Usage:
wallet_market_cancel_order <order_id> Cancel an order
Cancel an order
Parameters:
order_id (order_id, required): the ID of the order to cancel
Returns:
transaction_record
>> wallet_market_order_list BTC BTSX
TYPE QUANTITY PRICE BALANCE COST COLLATERAL ID
================================================================================================================================
cover_order 182,250.00000 BTSX 0.000027434842249657 BTC / BTSX5.00000000 BTC 4.99999999 BTC 243,000.00000 BTSX 2f7c01f9f56ff0d6286473ad0b68561b654ab0c0
cover_order 41,973.75000 BTSX 0.000027793561452098 BTC / BTSX1.16660000 BTC 1.16659999 BTC 55,965.00000 BTSX 8b41685adea121132b5546ebdd9dd054cc256aae
ask_order 27,393.75000 BTSX 0.000082135523613963 BTC / BTSX27,393.75000 BTSX 2.25000000 BTC N/A b91026170893374df40763a675c7537fe7812c37
Also did you change the format of the order ID? It is no longer BTSXxxxxxxxxxxxxxxxxxx...
-
Place the ID in quotes
Thanks, the double quotes ["] worked.
It worked without quotes for canceling the short order though.
-
Market loads for me now. I had to do a git clone <url> 0.4.13RC1 instead of git clone <url> then checkout master.
-
Done.
delegate.taolje
-
Done! :D
-
Running the GUI in the foreground I'm mostly seeing this spam by. I guess it's OK?
QPainter::end: Painter ended with 2 saved states
QObject::startTimer: Timers can only be used with threads started with QThread
/img/user.png
QPainter::end: Painter ended with 2 saved states
-
Running the GUI in the foreground I'm mostly seeing this spam by. I guess it's OK?
QPainter::end: Painter ended with 2 saved states
QObject::startTimer: Timers can only be used with threads started with QThread
/img/user.png
QPainter::end: Painter ended with 2 saved states
Interesting...
-
Upgraded.
mr.agsexplorer
mrs.agsexplorer
boombastic
-
upgrading
-
Delegate alecmenconi updated.
-
0.4.13 final has been released, and that it is the same as RC1 so RC1 users do not need to upgrade
https://github.com/dacsunlimited/bitsharesx/releases/tag/v0.4.13
-
Upgrade to 0.4.13 Complete.
-
done
hear.me.roar.lion
fire.and.blood.dragon
my.watch.begins.nightswatch
-
she.bitrose
is ok
+5% BTSX 0.4.13
-
calabiyau
neuronics
Upgrade to 0.4.13 running
-
Delegates:
www.minebitshares-com
www2.minebitshares-com
and seed nodes:
euseednode.minebitshares.com 54.77.51.177
auseednode.minebitshares.com 54.79.27.224
Updated to 0.4.13
-
web_wallet language detection is broken, right now it only checks ru, otherwise goes to default en. German and Chinese are skipped and will not be displayed.
Patch(ba7bf95 (https://github.com/BitShares/web_wallet/pull/320)) has been submitted to BitShares/web_wallet develop branch.
-
after updating to 0.4.13 now i don't see my open market orders.
rescan not worked.
-
(http://cdn.meme.li/instances/500x/54202651.jpg)
:P
-
(http://cdn.meme.li/instances/500x/54202651.jpg)
:P
Truly as good conspiracy theory as any... but no, I do not think so.
-
after updating to 0.4.13 now i don't see my open market orders.
rescan not worked.
Same here
-
after updating to 0.4.13 now i don't see my open market orders.
rescan not worked.
Same here
...
I can fix this tonight and dacsun can test out new gui hotfix push feature when they wake up
Sent from my SCH-I535 using Tapatalk
-
e.coin
bts.coin
bimin.coin
Upgraded
-
now.dacwin
future.dacwin
upgraded to 0.4.13
-
may I remind delegates to publish their version after backup upgrade. There is now a nice RPC call for that:
wallet_publish_version <publishing_account_name> [paying_account_name]
Very nice addition. I will no longer need to choose between having my delegate private key loaded into another wallet, or turning on transaction scanning long enough to publish.
-
delegate*.svk31 updated.
bitsharesblocks.com updated.
seednode updated. ( network_add_node "178.62.157.161:1776" add )
-
After updating the delegates on linux I was updating the binaries on Win7.
First time ever the wallet installed without glitches - installing - reindexing - connecting - syncing - YEAH ! Good experience.
Kudos to the dev-team +5%
-
upgraded to 0.4.13
-
after updating to 0.4.13 now i don't see my open market orders.
rescan not worked.
Same here
same
-
delegate bitcube updated to 0.4.13.
-
all of our delegates are out of active_delegates list . BM could you please vote them back in
love.ymca
support.ymca
ID NAME (* next in line) APPROVAL PRODUCED MISSED RELIABILITY PAY RATE PAY BALANCE LAST BLOCK
============================================================================================================================
13718 love.ymca 1.02417306 % 3511 5 99.86 % 100 % 2,525.29623 BTSX 449933
ID NAME (* next in line) APPROVAL PRODUCED MISSED RELIABILITY PAY RATE PAY BALANCE LAST BLOCK
============================================================================================================================
13719 support.ymca 0.57799522 % 1262 1 99.92 % 100 % 2,557.13563 BTSX 449935
Public Data:
{
"version": "0.4.13"
}
I have received numerous accusations that your account is a secret proxy for other accounts that are already in. I don't know whether they are true or not, but considering the number of people on the pending list and the relative newness of your account I have opted to let someone else in at this point in time.
I would suggest that you take some time to build a reputation as a unique player, join the mumble session and pitch your delegate.
-
There is a hotfix update for web gui, please update by clicking "File| Check for updates" in BitShares X client.
-
Nice, update done without any problems.
-
Prompted me as soon as I opened the client. It didn't error out but I don't know what the fix was so not sure if it worked :).
-
Prompted me as soon as I opened the client. It didn't error out but I don't know what the fix was so not sure if it worked :).
Fixed open orders display.
-
Prompted me as soon as I opened the client. It didn't error out but I don't know what the fix was so not sure if it worked :) .
Fixed open orders display.
Pretty slick way to update the client.
-
That was the fastest patch install I have ever seen!
Nice work 8)
-
dacsunlimited, could you make sure to use consisent tagging of releases? This one is "v0.4.XX", but every other release was "0.4.XX" I have scripts that are monitoring those tags, I can add a simple regex to clean it up, but just want to make sure I don't miss another one in the future.
Thanks!
-
My client won't connect, what do I do?
It just has a grey bar across the bottom that says not connected. I updated the client and updated again in the client, and agreed to also reindex the database.
-
I'm trying to cover a part of my short order, not the full amount.
Getting this error:
Unspecified (0) invalid hex character 'T'
-
I updated an hour ago and most of it works. All of my transactions are shown but there are no totals in the overview of my accounts. Not sure what to do about this.
-
I'm trying to cover a part of my short order, not the full amount.
Getting this error:
Unspecified (0) invalid hex character 'T'
This issue is being fixed and a soft update will be made available shortly.
-
I'm trying to cover a part of my short order, not the full amount.
Getting this error:
Unspecified (0) invalid hex character 'T'
This issue is being fixed and a soft update will be made available shortly.
Just updated, now I get an error saying:
Unknown market order(20011) cannot find market order!
But I can still see it on my open orders list.
Running windows 7
-
^^ just pushed a very recent fix for this.. try "file -> check for updates" or just restart
-
^^ just pushed a very recent fix for this.. try "file -> check for updates" or just restart
Using this new update, the error changed into this unknown order one
-
When I oppened the client, it asked me about the updated. I said yes and nothing happens. So I unlock the wallet and there is nothing showing the progress of the update. Then I check the current version to see if it was already updated and it's still at .12. Then I used the File| Check for updates. Chose yes but then my wallet locks and there is nothing showing the progress of the update again. So i unlock it once again and the same happens, still at .12. Also when i click File| Check for Updates it says there are no updates atm.
It's the first time doing this as I only downloaded the client recently. Am I doing something wrong?
-
the in-app updates are GUI updates only ... the core client needs to be updated by hand
known issue
https://github.com/BitShares/web_wallet/issues/322
//edit: ha .. this time I was faster than BM ... :P :P .. although only a block interval :)
-
When I oppened the client, it asked me about the updated. I said yes and nothing happens. So I unlock the wallet and there is nothing showing the progress of the update. Then I check the current version to see if it was already updated and it's still at .12. Then I used the File| Check for updates. Chose yes but then my wallet locks and there is nothing showing the progress of the update again. So i unlock it once again and the same happens, still at .12. Also when i click File| Check for Updates it says there are no updates atm.
It's the first time doing this as I only downloaded the client recently. Am I doing something wrong?
Updates are almost "instant" and only update the GUI and do not update the backend.
-
I'm trying to cover a part of my short order, not the full amount.
Getting this error:
Unspecified (0) invalid hex character 'T'
This issue is being fixed and a soft update will be made available shortly.
Just updated, now I get an error saying:
Unknown market order(20011) cannot find market order!
But I can still see it on my open orders list.
Running windows 7
To clarify, this change of error was after the recent soft update.
I just tried canceling an ASK and that worked fine.
But trying to cover the short results in: Unknown market order(20011) cannot find market order!
I don't know if it's relevant, but I made the short in 4.13 (before soft update)
And instead of Marging Call, It says market.order_type.margin_order in the GUI.
-
There is a hotfix update for web gui, please update by clicking "File| Check for updates" in BitShares X client.
Displayed a prompt to update with the program running. Did this do the trick?
If 'Yes' pretty, prettyCOOL!!!
+5%
Older orders displayed - check.
Checking new orders behavior.... displayed - check.
-
There is a hotfix update for web gui, please update by clicking "File| Check for updates" in BitShares X client.
Displayed a prompt to update with the program running. Did this do the trick?
If 'Yes' pretty COOL!!!
+5%
No it didn't
-
I'm trying to cover a part of my short order, not the full amount.
Getting this error:
Unspecified (0) invalid hex character 'T'
This issue is being fixed and a soft update will be made available shortly.
Just updated, now I get an error saying:
Unknown market order(20011) cannot find market order!
But I can still see it on my open orders list.
Running windows 7
To clarify, this change of error was after the recent soft update.
I just tried canceling an ASK and that worked fine.
But trying to cover the short results in: Unknown market order(20011) cannot find market order!
I don't know if it's relevant, but I made the short in 4.13 (before soft update)
And instead of Marging Call, It says market.order_type.margin_order in the GUI.
I have reproduced it here... fix is under way.
-
4.13 up and running. Great new features!
-
There is a hotfix update for web gui, please update by clicking "File| Check for updates" in BitShares X client.
Displayed a prompt to update with the program running. Did this do the trick?
If 'Yes' pretty COOL!!!
+5%
No it didn't
It seems it did it for me... still displayed after a restart. Canceling them works too.
What is not working - covering? Hope I never have to use the feature :)
Yee same here... covering not working
hoping for fast fix...
-
the in-app updates are GUI updates only ... the core client needs to be updated by hand
known issue
https://github.com/BitShares/web_wallet/issues/322
//edit: ha .. this time I was faster than BM ... :P :P .. although only a block interval :)
Okay, I got it now. Thanks!
-
completed 0.4.14
please vote me up
btsx.outofcontrol & mtang.outofcontrol
-
completed 0.4.14
please vote me up
btsx.outofcontrol & mtang.outofcontrol
I see it released in their github but has it been announced yet?
-
completed 0.4.14
please vote me up
btsx.outofcontrol & mtang.outofcontrol
I see it released in their github but has it been announced yet?
Me as well so I've not cut-over yet. Need to sleep soon so I will have to probably do it tomorrow. I think they normally do a separate thread for each one.
-
Why was this release not announced?
BTW fixes for me what it is supposed to fix!
-
My 0.4.13 wallet can not cancel the short orders of BitCNY...
-
My 0.4.13 wallet can not cancel the short orders of BitCNY...
Think this is what 0.4.14 is addressing.
It's about covering: https://bitsharestalk.org/index.php?topic=8738.msg113291#msg113291
-
My 0.4.13 wallet can not cancel the short orders of BitCNY...
What is the error you are getting?
A lot of order/account IDs need to be in quotes since 0.4.13. {some json thing is my uneducated guess}
-
The client/GUI keeps flashing:
RPC Server Error: In method 'wallet_market_order_list': Assert Exception (10)
In the bottom bar.
win7/32bit v0.4.14
-
That is fixed and will be included next push
Sent from my SCH-I535 using Tapatalk
-
My 0.4.13 wallet can not cancel the short orders of BitCNY...
What is the error you are getting?
A lot of order/account IDs need to be in quotes since 0.4.13. {some json thing is my uneducated guess}
Just no response after clicking the "cancel" button, even the same by several times.
-
Don't know if anyone has posted this bug yet but I had BitUSD placed for sale, updated the wallet and now the order is gone? :(
-
My 0.4.13 wallet can not cancel the short orders of BitCNY...
What is the error you are getting?
A lot of order/account IDs need to be in quotes since 0.4.13. {some json thing is my uneducated guess}
Just no response after clicking the "cancel" button, even the same by several times.
Try the console, if you are really trying to cancel it. I mean if you are not mainly reporting a bug.
-
Whats the command in the console please?
-
Whats the command in the console please?
Do you mean the command to cancel an order?
wallet_market_cancel_order <order_id>
to get the order ID:
wallet_market_order_list <base_symbol> <quote_symbol> [limit] [account_name]
this will be
wallet_market_order_list USD BTSX //for your bitUSD orders
[edit] order id might need to be in quotes.
-
Don't know if anyone has posted this bug yet but I had BitUSD placed for sale, updated the wallet and now the order is gone? :(
I having a similar problem.
https://bitsharestalk.org/index.php?topic=8756.0
-
Updated to "client_version": "0.4.14"
-
Hey guys! I am new to Bitshares but i have been in the BTC world for 2 years now!
Ok i really need some help updating the client in Linux.
Can anyone please tell me the procedure to do this?
Thanks, Voltago!
-
My client won't connect, what do I do?
It just has a grey bar across the bottom that says not connected. I updated the client and updated again in the client, and agreed to also reindex the database.
I'm having the same issue you describe. Updated the client and reindexed, but it's not connecting. Gray bar at bottom.
EDIT: I left it on while doing something else. Eventually (after 5 minutes or so of apparent inactivity) it did connect and started synching/scanning the transactions again. There is a pulse. But I'm leaving my posting here because others may have a similar issue.
-
Hey, I decidet to install ubuntu again and now it's fast as a weazel. It's nice to have such a fresh OS and the shrine aka BitSharesX is in front of me shining. Cass, could you make a golden skin one day? Now I just have to play around. It would be good to sit next to someone and learn from watching but you cannot have everything in life ;)
-
I compiled the version 0.4.14
but after checking the tag 0.4.14:
git checkout 0.4.14
this error appears:
error: pathspec '0.4.14' did not match any file(s) known to git.
should I trust this release?
-
Just type git checkout master and it will work (worked for me)
-
I compiled the version 0.4.14
but after checking the tag 0.4.14:
git checkout 0.4.14
this error appears:
error: pathspec '0.4.14' did not match any file(s) known to git.
should I trust this release?
They changed the version tag naming convention.
$ git tag
...
0.4.12
0.4.13-RC1
...
v0.4.13
v0.4.14
-
Although my server have 2 GB ram, it gives the following error;
[ 64%] Building CXX object libraries/blockchain/CMakeFiles/bts_blockchain.dir/chain_database.cpp.o
virtual memory exhausted: Cannot allocate memory
make[2]: *** [libraries/blockchain/CMakeFiles/bts_blockchain.dir/chain_database.cpp.o] Error 1
make[1]: *** [libraries/blockchain/CMakeFiles/bts_blockchain.dir/all] Error 2
make: *** [all] Error 2
-
Search for "swap file" .. either in the forum or in google