Topic: Armory - Discussion Thread - page 176. (Read 521749 times)

A few days ago I downloaded and installed Armory on my windows 7 laptop, but I can't seem to get it to run in online mode.  Whenever I try to run Armory it says it can't detect the satoshi client.  I have Bitcoin-QT (version 6.2-beta) running and the block-chain is synced with the network.  Is there anything big I'm missing or do I have a unique problem?

Try this version:

http://dl.dropbox.com/u/1139081/ArmoryTestingReleases/armory_0.82.2_i386.deb

I recompiled on a 10.04-32bit system.  That should work.   I'll replace it on the downloads page if there are no complaints.

Interesting... That error hasn't happened in a while, and used to be related to python versions, but I had fixed that. 

This was compiled on 12.04-32bit, which was a change I made a while ago (but no official releases).  I wonder if I just had no 10.04-32bit testers who ran into it...?

I'll look into it tonight. 

It depends on your definition of "alternative."  I have the Satoshi client installed & running, but I haven't touched it in 6 months.  Armory replaces all user-facing functionality 100% (just not the networking).  So, it is essentially an alternative.  It just requires an extra program to be running in the background.

I don't want to be pushy, I wast just genuinely surprised that you've been using armoryengine so long but never actually used Armory itself.  To say that it is "simpler" without it is like saying life is "simpler" without a lock on my front door because I don't have to get out my keys when I come home  

If you have Satoshi client running anyway, you should try it.  The deterministic wallets + paper backups alone are worth it (IMO).

As I understand it, I either run the satoshi client, or I run the satoshi client plus armory.

The former seems the simpler option to me.  It's not like armory is an alternative, it's an add-on.  Am I right?

Just out of curiosity:  why not? 

I've been using the 'logger' branch from the git repository, rather than a 0.82.2 download, and it works for me running my modified SatoshiDice analysis script.

I don't run Armory itself though.

Request for comments:

Any problems experienced by anyone with 0.82.2?  (besides wachtwood's networking issue)

Just want to know if I should have any reservations uploading the installers as-is to github and doing an official release.

I have a warning about it if you go to "File->Export Log File".  I am very careful never to log private keys or passwords.  My goal is ultimately to catch error messages with the appropriate context around them (what function calls were made leading up to it).  But such context may include address/tx information.

So, there are privacy implications.  I copy full transactions (signed or unsigned) into the log file, so that I can later identify if a transaction was malformed, or selected inputs in an invalid way, etc.  This means I would see some addresses that you own.  The point of the warning is to let you know about these privacy implications and give you a chance to sanitize the file yourself before you send it to me.  In many cases, I don't actually need the tx information, unless it's a tx-related bug, etc.  In most cases, I only need the error message itself.  But I can't have 100 different log levels to accommodate every possible situation.  That is a balance I needed to strike when setting up the logging system...


P.S. - If you're really curious about what gets logged, you can search armoryengine.py, ArmoryQt.py and qtdialogs.py for the any of the following strings:  LOGDEBUG, LOGINFO, LOGWARN, LOGERROR, LOGCRIT or LOGPPRINT.  The log file is exclusively constructed from calls to those functions.

Okay, thanks, just let me know and I'll run it. What exactly are you logging? (should I use a test wallet, can you see my password, do you have access to private keys etc.)

Okay, now I remember.  I end up in a lot of PM/email conversations about random bugs and couldn't remember for sure which and how many bugs you reported  

So, Armory on your system thinks it never completed the handshake with the Satoshi client and refuses to send transactions.  I don't know any other way to diagnose this other than adding a ton of log-file output and having you run it (I'll just add a separate logger and CLI flag to turn it on).  I'll try to get to that tonight. 

Oh sorry since we had a PM exchange I figured you'd remember


And subsequently we had  a PM discussion and you said you'd look into it after the holiday. It had something to do with the client thinking it lost contact with the Satoshi client while it actually didn't and the Satoshi client is also is actually sending data to the Armory client and it is accepting this data to. However it still is in a disconnected state and therefore blocking actions that need an active connection.

Yeah, I'll merge it to master when I'm ready for a real release. 




Are you still referring the networking issue?  Or a different issue?  I'll try to do some more investigative work on the networking issue (or at least expand the logging for grabbing network messages).  I wouldn't have expected this release to fix it, unless you're referring to something else.

Just to report: I tried it and still have the same problem.

It looks to me like the recent changes are only on the 'logger' branch.

Working fine now with the new version

Thanks!

What branch is it built from?

The ArchLinux package builds from git, but needs to know which branch to start with (preferably a stable one, so that the build instructions don't need to be changed at every release).

Will that be put into master?

I think if you have the code wait for you to hit return after opening the blockchain files but before scanning them, and then wait for a block or two to be received while it's waiting, you'll see the bug happen.

I've not had a chance to test your fix yet, but if you used my change then I'm guessing it will work for me.  I've still had no crashes since making the change myself.

Please help sanity-check 0.82.2 before release!

Armory 0.82.2 - Windows-64bit *.msi installer
Armory 0.82.2 - Windows-32bit *.msi installer
Armory 0.82.2 - Linux64 Debian/Ubuntu Package
Armory 0.82.2 - Linux32 Debian/Ubuntu Package


This should fix most of the SelectCoins problems (thanks to jl2012 who sent me a watching-only wallet that exhibited the buggy behavior -- using that, I found and fixed the bug in about 30 minutes!).  Dooglus' fix is implemented, though I can't really test it since I can't replicate it myself. I also added a small fix to transaction export-to-csv to better handle/display sent-to-self transactions.

If you previously had any problems sending coins, please try the new version!  I expect all of those problems to go away! 

I will give this a day or two and then it will be an official release.  The debugging code has been in testing for long enough (and uncovered enough bugs) that I finally feel comfortable releasing it (and all future bug reports will get much easier!).

This looks like it might be related to the bug that I referenced in my previous post.  Though, the error I would expect to see would be "The value you have specified is valid, but the required transaction fee exceeds your remaining balance..." (because you specified bal-0.0005 and fee of 0.0005, but Armory needed to increase the fee to 0.001 and could not do so.

What version are you using?  Have you upgraded to 0.82.1?  If so, can you send me the log file?  Usually when a button does nothing, it's because an error was triggered and the function that was called just exits silently without finishing the job.  This will show up in the log file.  You can manually copy the log file from your ARMORY_HOME_DIR or you can use the main window "Export Log File".  Feel free to sanitize it before posting or emailing it to me.  

If not, then wait until tonight:  I will release 0.82.2 which has a bug fix that might resolve this.  If it doesn't, at least there will be a log file.


I haven't actually released the bug fix for that yet.  I got distracted last night, and will do it tonight instead. It will be 0.82.2.  All the SelectCoins errors should go away (hopefully, apetersson's issue, too!).


EDIT: Website should be back up.  There was a payment processing error that is resolved now.  Whoops.