I work with China. In February everything stops because the Chinese New Year. No way they ship in February.
So you claim, That my electric companies telephone lines will not be open due to Chinese New Year? And that (for the lulz) the police services across the world will all go on holliday on at the same time? (not to say that they will stop, Just that they would swap to Holliday style hours and active employees) And that my nearby Walmart will be closed for the CNY? And that i wont beable to buy booze due to the CNY? Only china related things are going to be affected by the CNY, Seriously you're being a total fool here. And incase you were reffering Only to shipping, Only China related shipments are going to slowdown, seriously. Goahead and tell me that my package (HDD) from Canada(Richmond BC), through Purolator(delivery service), To an island in Canada [Victoria BC(where i live)] is going to get slown down by the CNY. I would love to hear you explanation as to how my package is going to stop moving when the CNY occurs. MAYBE it MIGHT slowdown because of..... Hmm.... Chinas stuff not moving? how? Obviously, he is talking about everything in China. He lives there. However, have you tried to buy cheap crappy shit on ebay lately? All the sellers are away for the next 2-3 weeks and have their stores in a hold mode. How the fuck am I going to get my cute owl design silicone case for my iphone 4s? |
|
|
|
|
I went ahead and upgraded my public node to the .8 RC and in the past 36 hours, I have noticed that I have had an increase of almost 3x in the amount of bandwidth being used. it went from 2-3 GB outgoing per day to almost 10 GB outgoing per day. Is that because of the bloom filtering? Or just more people upgrading and testing out the RC?
|
|
|
|
Meanwhile I was proven right but the same shills are still here repeating that "I'm unprofessional".
Well, to their credit, you are a horrible troll. +1 Maybe if you weren't such an.... asshole, maybe people would listen to you? |
|
|
|
|
Wait wait, I don't like the delete after 15 seconds as much as I like delete messages previous to x minutes.
|
|
|
|
|
Had some ideas pop up in the chat room.
Anyone can delete all messages any time. What about making it wait like 10-15 seconds before it deletes everything so people can see the last messages?
Another idea, delete everything older than x minutes. So the last couple of minutes are still available.
And lastly, what about an option to autodelete from the server when everyone leaves?
Lots of fun. No proof of identity of course anyone can be anyone. But absolutely shows a KISS idea.
|
|
|
|
|
Someone make a chat so I can join it.
There is no proof though that you are not storing IP addresses though, is there?
|
|
|
|
|
Cool, but how do you make money from it?
|
|
|
|
Error upgrading on Ubuntu 11.04 server. ************************
EXCEPTION: St9bad_alloc
std::bad_alloc
bitcoin in ProcessMessages()
************************
EXCEPTION: St9bad_alloc
std::bad_alloc
bitcoin in ThreadMessageHandler()
terminate called after throwing an instance of 'std::bad_alloc'
what(): std::bad_alloc
Aborted
It had the full block chain, was upgrading, not sure where it was in the blocks > 170k I know that for sure... |
|
|
|
|
For the last few minutes site has been crawling for me, but no errors. Each page taking 30-45 seconds to load.
|
|
|
|
I haven't been seeing any. Do they appear at any particular times, or on any particular sorts of pages?
Theymos, I've been seeing them too. But not a huge amount of them. They will pop in between 12-4 EST. Lasting maybe 5 minutes. When I return there are lots of posts like it wasn't effecting everyone while I was gone. |
|
|
|
Last time (10 days ago or so) it took me a full week to download the blockchain.
Hope the new client is on its way indeed.
RC1 of .8 is out and being tested. If you addnode and connect to a high speed node, you can download the blockchain in less than an hour and have a full node up and running on a fast computer. Older ones with random connections to random peers may take a few hours still but much better than a day to a week. |
|
|
|
|
Got mine as well, thanks.
|
|
|
|
The crash-on-exit bug could be this issue: https://github.com/bitcoin/bitcoin/issues/2204We may have to live with it for the 0.8 release, and fix it in the next release, because there is a high risk that fixing it will cause more problems than it solves. Not sure if this is exactly what happened, but it only did it on one machine. After it started back up, it is now working fine. I closed it after it caught up to the block chain and no error. I closed out of one other instance of bitcoin and it didn't error. Opened it back up. I'm going to leave one running and the other three I'm going to close every 24 hours or so and see if it opens up again. Besides giving it extra work the first time it closed, it didn't look like it really had any other side effects. If there is anything I can do to help squash it or test it, let me know. The ones that don't reproduce consistently are difficult. This machine has identical specs as the other Win 7 machine and the first one didn't do it. Not sure. |
|
|
|
no payment so far
Same here. I sent my address by PM. Let me know if you didn't get it. |
|
|
|
I saw on the S.DICE thread earlier today that Erik's recent "dumps" were a result of a large S.DICE private investor cashing out by selling to Erik, and Erik passing on a part of his shares to the market. My first thought was "I wonder if HE was the whale?".
But how do you prove it? |
|
|
|
...Professionalism... This made me chuckle, considering the author. +1 |
|
|
|
All four of the first machines are running just fine. I did another test on a more recent CPU plenty of ram running Windows 7. I let it run overnight and download the whole blockchain. This morning I ran windows updates that were pending and prepared for a reboot. The block chain had not finished downloading all of the way yet (I used add IP from a local node for all these, probably why my results were faster than most others posted here) I did a file exit on Bitcoin-qt and got this exception: A fatal error occurred. Bitcoin can no longer continue safely and will quit.
Exception: St9pad_alloc
std:bad_alloc
C:\Program Files\Bitcoin\bitcoin-qt.exe in Runaway exception These are the last entries in the debug log SetBestChain: new best=000000000000018829028b3af6d47eac9dab3f4b233c77aff1ee2262fcd0faaa height=214069 work=687730958631335352866 tx=10451422 date=2012-12-28 19:24:59
SetBestChain: new best=000000000000002aeab1c5b9fc27e14f759ab16a3e4cde600d98718b93e50416 height=214070 work=687743756268435510981 tx=10451918 date=2012-12-28 19:35:21
SetBestChain: new best=000000000000057d76f8d7a62f3de9a874055874614c6423fce82f60b0177d9a height=214071 work=687756553905535669096 tx=10452418 date=2012-12-28 19:40:47
I opened Bitcoin back up and it pegged all cores of the CPU for a while. I had some stuff minimizing and maximizing so I'm not sure what the splash screen said that it was doing. This was much longer by a significant amount vs. the other machines when I close Bitcoin and open them back up. In fact, it is still not open now after about 10 minutes and after it opens I'll post more details. But for now, there is a crash on RC1 with Windows 7. It did not crash until I asked it to shut down. I checked the resource usage, Bitcoin-qt was using about a gig of ram, machine has 8 GB and wasn't even at 50% utilization for ram. 45 minutes later it starts up and finishes the block chain very quickly. I closed it down and opened it back up just fine nice and fast. Not sure what other information I can provide about this but it seems that everything is okay now. |
|
|
|
All four of the first machines are running just fine. I did another test on a more recent CPU plenty of ram running Windows 7. I let it run overnight and download the whole blockchain. This morning I ran windows updates that were pending and prepared for a reboot. The block chain had not finished downloading all of the way yet (I used add IP from a local node for all these, probably why my results were faster than most others posted here) I did a file exit on Bitcoin-qt and got this exception: A fatal error occurred. Bitcoin can no longer continue safely and will quit.
Exception: St9pad_alloc
std:bad_alloc
C:\Program Files\Bitcoin\bitcoin-qt.exe in Runaway exception These are the last entries in the debug log SetBestChain: new best=000000000000018829028b3af6d47eac9dab3f4b233c77aff1ee2262fcd0faaa height=214069 work=687730958631335352866 tx=10451422 date=2012-12-28 19:24:59
SetBestChain: new best=000000000000002aeab1c5b9fc27e14f759ab16a3e4cde600d98718b93e50416 height=214070 work=687743756268435510981 tx=10451918 date=2012-12-28 19:35:21
SetBestChain: new best=000000000000057d76f8d7a62f3de9a874055874614c6423fce82f60b0177d9a height=214071 work=687756553905535669096 tx=10452418 date=2012-12-28 19:40:47
I opened Bitcoin back up and it pegged all cores of the CPU for a while. I had some stuff minimizing and maximizing so I'm not sure what the splash screen said that it was doing. This was much longer by a significant amount vs. the other machines when I close Bitcoin and open them back up. In fact, it is still not open now after about 10 minutes and after it opens I'll post more details. But for now, there is a crash on RC1 with Windows 7. It did not crash until I asked it to shut down. I checked the resource usage, Bitcoin-qt was using about a gig of ram, machine has 8 GB and wasn't even at 50% utilization for ram. |
|
|
|
|
Show Posts
