Pages:
Author

Topic: Bitcoin Core 0.9.2.1 has been released - page 6. (Read 27416 times)

legendary
Activity: 1334
Merit: 1004
TTM
June 18, 2014, 07:32:57 AM
#24
OS X version have font bug. I cant see addresses
legendary
Activity: 1512
Merit: 1012
June 18, 2014, 06:14:52 AM
#23
Please get an OS that is still supported.

bitcoin-core is not tested on winXP ?
(it's real question)
hero member
Activity: 508
Merit: 500
June 18, 2014, 04:07:19 AM
#22
Getting closer and closer to 1.0
Can't wait!
copper member
Activity: 1498
Merit: 1528
No I dont escrow anymore.
June 18, 2014, 02:57:23 AM
#21
-snip-
System : windows XP 32 bits
-snip-

Please get an OS that is still supported.
sr. member
Activity: 434
Merit: 250
June 18, 2014, 12:10:50 AM
#20
Good News and Great work. But can someone kindly state the most important updates for the laymen amongst us.
legendary
Activity: 1512
Merit: 1012
June 17, 2014, 05:32:50 PM
#19
Crash at the shutdown (when i want close normally bitcoin-core).



Code:

2014-06-17 22:28:12 Added time data, samples 5, offset -1 (+0 minutes)
2014-06-17 22:28:12 nTimeOffset = +0  (+0 minutes)
2014-06-17 22:28:21 Requesting shutdown
2014-06-17 22:28:21 Running Shutdown in thread
2014-06-17 22:28:21 addcon thread interrupt
2014-06-17 22:28:21 dumpaddr thread stop
2014-06-17 22:28:21 msghand thread interrupt
2014-06-17 22:28:21 net thread interrupt
2014-06-17 22:28:22 opencon thread interrupt
2014-06-17 22:28:22 Shutdown : In progress...
2014-06-17 22:28:22

************************
EXCEPTION: N5boost16exception_detail10clone_implINS0_19error_info_injectorINS_6system12system_errorEEEEE      
cancel: Le descripteur de fichier fourni n'est pas valide      
G:\Bitcoin\bitcoin-qt.exe in Runaway exception      

2014-06-17 22:28:37 CDBEnv::EnvShutdown : Error 22 shutting down database environment: Invalid argument
Requesting initialize
Running AppInit2 in thread
2014-06-17 22:29:01


System : windows XP 32 bits with all windows update installed ( automated : http://www.skyminds.net/pack-de-correctifs-windows-xp-post-sp3 )
Solo-mining with BFGMiner activate.
I use redirection of the blockchain folder (fixed drive).
I use the "no wallet" feature (node system).

old version 0.9.1 don't do this.
legendary
Activity: 1400
Merit: 1000
June 17, 2014, 04:52:07 PM
#18
Great work
newbie
Activity: 27
Merit: 0
June 17, 2014, 03:34:37 PM
#17
Awesome! Thank you core developers! Didn't get the chance to test the 9.2 RC, but will take this for a spin in short time.
legendary
Activity: 1456
Merit: 1001
This is the land of wolves now & you're not a wolf
June 17, 2014, 11:24:04 AM
#16
Are any of you using both Bitcoin Core and Litecoin QT on the same computer?   I am running Litecoin QT from an ultrabook with a dinky SSD harddrive, so I don't want to fill the whole thing up with blockchains..
hero member
Activity: 812
Merit: 1022
No Maps for These Territories
June 17, 2014, 10:33:19 AM
#15
The font change looks like crap...I'm sure I'll get used to it though.

(Mac OSX)
Can you post a screenshot?
legendary
Activity: 1610
Merit: 1004
June 17, 2014, 08:53:54 AM
#14
The font change looks like crap...I'm sure I'll get used to it though.

(Mac OSX)
hero member
Activity: 812
Merit: 1022
No Maps for These Territories
June 17, 2014, 06:39:01 AM
#13
Can we leave getinfo untouched in long run too ? Like in Java Vector is deprecated, but we can still have it. I mean the old codes wont crash.
That's possible, but at some point it will lose information. For example, when the wallet is split off to another project, it will no longer contain wallet information. So no matter what you use it for, it will lose its remaining usefulness over time. At a certain point it's better to just remove the call and clean up the code a bit...
hero member
Activity: 1582
Merit: 502
June 17, 2014, 06:28:29 AM
#12
Nothing yet. They just made new commands that make more sense. The people behind the APIs have time to update their code accordingly so everything goes smoothly when getinfo is removed.
Exactly. It will take a very long time until getinfo is actually removed. There is no hurry. But no new information will be added to it anymore, whereas the new calls provide more (and more specific) information so it makes more sense to use them going forward.

Can we leave getinfo untouched in long run too ? Like in Java Vector is deprecated, but we can still have it. I mean the old codes wont crash.

The way I see it, it's much better for you when handling data with the new commands.
Much faster too.

legendary
Activity: 2394
Merit: 1216
The revolution will be digital
June 17, 2014, 06:20:33 AM
#11
Nothing yet. They just made new commands that make more sense. The people behind the APIs have time to update their code accordingly so everything goes smoothly when getinfo is removed.
Exactly. It will take a very long time until getinfo is actually removed. There is no hurry. But no new information will be added to it anymore, whereas the new calls provide more (and more specific) information so it makes more sense to use them going forward.

Can we leave getinfo untouched in long run too ? Like in Java Vector is deprecated, but we can still have it. I mean the old codes wont crash.
hero member
Activity: 812
Merit: 1022
No Maps for These Territories
June 17, 2014, 06:13:17 AM
#10
Nothing yet. They just made new commands that make more sense. The people behind the APIs have time to update their code accordingly so everything goes smoothly when getinfo is removed.
Exactly. It will take a very long time until getinfo is actually removed. There is no hurry. But no new information will be added to it anymore, whereas the new calls provide more (and more specific) information so it makes more sense to use them going forward.
copper member
Activity: 1498
Merit: 1528
No I dont escrow anymore.
June 17, 2014, 06:11:16 AM
#9
GooD News Smiley

Why do u think `getinfo` is hodge-podge ? Wink
Well it combines information from different subsystems - the wallet, P2P networking, block chain handling, etc. It doesn't fit in the more modular approach that we have in mind. It is also slow to acquire all the locks and gather the information.


What would happen to the APIs using getinfo data ?


Nothing yet. They just made new commands that make more sense. The people behind the APIs have time to update their code accordingly so everything goes smoothly when getinfo is removed.

---------------

Optionally add third party links to transaction context menu

Had no time to play with the new client yet, but this sounds like an invitation for phishing. nice feature to have.
legendary
Activity: 2394
Merit: 1216
The revolution will be digital
June 17, 2014, 05:27:22 AM
#8
GooD News Smiley

Why do u think `getinfo` is hodge-podge ? Wink
Well it combines information from different subsystems - the wallet, P2P networking, block chain handling, etc. It doesn't fit in the more modular approach that we have in mind. It is also slow to acquire all the locks and gather the information.


What would happen to the APIs using getinfo data ?
sr. member
Activity: 392
Merit: 250
June 17, 2014, 05:16:57 AM
#7
GooD News

Great work. Thanks for information
full member
Activity: 182
Merit: 101
June 17, 2014, 05:13:34 AM
#6
news info good Smiley

great work thanks Smiley
legendary
Activity: 1540
Merit: 1000
June 17, 2014, 04:50:25 AM
#5
I was suspicious at first but then I realised where the links were, I'll wait for an announcement on Bitcointalk before I click anything though lol Tongue
Pages:
Jump to: