0 Members and 1 Guest are viewing this topic.
When using "burn records" on someone's wall, why is it changing to "against" every time no matter what is selected (for/against)?Which color indicates your selection (green/white)? No matter which we try it ends up as same result, against.
Short margin calls on expiry will buy up any asks up to 10% above feed.
Quote from: tonyk2 on April 11, 2015, 01:23:27 pm Take a look at the bitUSD:BTS market right now. The market matching seem to not be fixed after all feed 222.3416 Shorts at that price do not match with the buy bitUSD at 226 or 225;Expired shorts do not match either.Yea I've been watching this too for the last hour while working on the wallet, what makes everything even stranger is that there are trades happening but at ~246 BTS/bitUSD, more than 10% above the feed price at the time.Here's a dedicated thread: https://bitsharestalk.org/index.php/topic,15668.msg201291.html#msg201291
Take a look at the bitUSD:BTS market right now. The market matching seem to not be fixed after all feed 222.3416 Shorts at that price do not match with the buy bitUSD at 226 or 225;Expired shorts do not match either.
hmm, I did make an account on a mac computer a while ago and then made another with the same name on my PC...
Is it just me, or is BTS:NOTE screen much much much slower than BTS:BitUSD?
I recently hit some issues with 0.8.I tried enabling RPC and this triggered a full blockchain re-download which took a few hours. While this was happening, I set the logout automatically to a really big number like 40000000000 or something. This triggered a bug rendering the wallet completely unusable with the timing out screen rapidly appearing and disappearing. I couldn't fix this from removing the config etc and in the end had to restore from a backup wallet.
Quote from: xeroc ¯\_(ツ)_/¯ on April 01, 2015, 05:00:53 pmIn the folder "Library/Application Support/BitShares" there is a subfolder called "chains" ... remove just that one!!Why there isn't a command to do that is beyond me. It's like a mandatory step for every upgrade.
In the folder "Library/Application Support/BitShares" there is a subfolder called "chains" ... remove just that one!!
How exactly should I perform these actions in a OSX environment???thanks
Quote from: Tuck Fheman on March 28, 2015, 06:59:42 amQuote from: Bitty on March 28, 2015, 05:55:35 amBlockchain stuck at block 2074788.Mac client.Upgraded to 0.8. What can I do?backup walletremove chain folderrestart client and let resyncworks for usthanks how does one back up the client without making mistakes?
Quote from: Bitty on March 28, 2015, 05:55:35 amBlockchain stuck at block 2074788.Mac client.Upgraded to 0.8. What can I do?backup walletremove chain folderrestart client and let resyncworks for us
Blockchain stuck at block 2074788.Mac client.Upgraded to 0.8. What can I do?
Quote from: yellowecho on March 28, 2015, 06:41:19 pmFor some reason 0.8.0 is running extremely slow for me now especially the NOTE and other UIA markets. It's not crashing but seems very unstable. I'm running 16GB RAM so its not a memory issue but acts similar. Any ideas?Which UI version are you on? I suggest removing UI updates from the file menu. You can get them back just as easily, so it's worth a try.I'm on 0.8.1, but it seemed like the 0.8.1-a update had a few some issues.
For some reason 0.8.0 is running extremely slow for me now especially the NOTE and other UIA markets. It's not crashing but seems very unstable. I'm running 16GB RAM so its not a memory issue but acts similar. Any ideas?
Quote from: monsterer on March 30, 2015, 10:18:21 amMy win 0.8.0-a (and 0.8.0 builds) are stuck on the wrong fork, is there anything I can do without having to delete and regrab the entire chain?restart with Code: [Select]--rebuild-indexmay only work with the bitshares_client.exe (nonGUI)
My win 0.8.0-a (and 0.8.0 builds) are stuck on the wrong fork, is there anything I can do without having to delete and regrab the entire chain?
--rebuild-index
Bad CastInvalid cast from object_type to stringgetStackTrace@app.js:39:3875 ○ request@app.js:44:23145 ○ get_block_transactions@app.js:43:824 ○ app.js:39:25606 ○ i@app.js:7:45735 ○ app.js:7:45907 ○ $eval@app.js:7:82135 ○ $digest@app.js:7:80649 ○ $apply@app.js:7:82409 ○ f@app.js:7:16490 ○ r@app.js:7:25269 ○ onload@app.js:7:258097 bad_cast_exception: Bad CastInvalid cast from object_type to string {"type":"object_type"} bitshares variant.cpp:471 fc::variant::as_string
.bitshares/logs# du -h -d14.0K ./blockchain4.0K ./rpc243M ./default620M ./p2p863M .
I'm also getting "Network Problems" again (had it last night, but ws Ok this morning - but now back). Is there a way to check how many delegates are participating in my case and whether or not I am on a fork?
"blockchain_head_block_age": "8 seconds old","blockchain_average_delegate_participation": "82.11 %",
Oh man this version is awesome, so so smooth! Nice work OSX Yosemite with 8GB ram.When was the involuntary 0.1BTS receive fee decided on? I think this should be re-thought because at the moment. there's nothing stopping a rich twisted person from setting their transaction fee to 0.1 and sending <0.1 payments to people thus reducing their balance overall.
Hasn't connected to the network in over a day on my OS X.Still getting a call price error, but I do not know if that is a result of the blocks not being synced.
Linux GUI version 0.8 crashed. Previous version 0.7 works. (tested on Ubuntu 14.04)Code: [Select]Loading config from file: /home/gabo/.BitShares/config.jsonQSslSocket: cannot resolve SSLv2_client_methodQSslSocket: cannot resolve SSLv2_server_method/index.html/css/app.css/js/app.js/locale-en.json/img/xts-logo-xl-white-shadow.png/img/logo-ico.svg/img/xt-background.jpg/webfonts/opensans-regular.woff/webfonts/fontawesome-webfont.woff/img/logo-ico.svgQObject::startTimer: Timers can only be used with threads started with QThreadQPaintDevice: Cannot destroy paint device that is being paintedSegmentation fault
Loading config from file: /home/gabo/.BitShares/config.jsonQSslSocket: cannot resolve SSLv2_client_methodQSslSocket: cannot resolve SSLv2_server_method/index.html/css/app.css/js/app.js/locale-en.json/img/xts-logo-xl-white-shadow.png/img/logo-ico.svg/img/xt-background.jpg/webfonts/opensans-regular.woff/webfonts/fontawesome-webfont.woff/img/logo-ico.svgQObject::startTimer: Timers can only be used with threads started with QThreadQPaintDevice: Cannot destroy paint device that is being paintedSegmentation fault
One of the things I like about the latest upgrades, is there's no need to re-index the entire blockchain anymore. Is this a new feature?
so much faster, so much stronger than poor old 0.7.0!
better than 0.7.0 for me personally (win7/i7/8gb). faster load. market swapping with everything loading up within 10 seconds at worst, 3-5 seconds on most tries.i was never affected adversely by glitches in prior versions, so i can't comment on any of those fixes. it's just getting smoother with each new version for me!
https://github.com/BitShares/bitshares/releases/tag/bts%2F0.8.0