Currently it is only possible to use walletpassphrase to unlock the wallet when bitcoin is started in server mode.
Almost everything that manipulates the wallet in the RPC console (for example, importprivkey) needs the wallet to be unlocked and is thus unusable without -server.
This is pretty unintuitive to me, and I'm sure it's even more confusing to users.
Solve this with a very minimal change: by making the GUI start a dummy RPC thread just to handle deadline timers.
Currently it is only possible to use `walletpassphrase` to unlock the
wallet when bitcoin is started in server mode.
Almost everything that manipulates the wallet in the RPC console
needs the wallet to be unlocked and is thus unusable without -server.
This is pretty unintuitive to me, and I'm sure it's even more confusing
to users.
Solve this with a very minimal change: by making the GUI start a
dummy RPC thread just to handle timeouts.
Automatic sanity-testing: PASSED, see http://jenkins.bluematt.me/pull-tester/a8db31c83d6a43e07f741f7f61b1bf0df87621c7 for binaries and test log. This test script verifies pulls every time they are updated. It, however, dies sometimes and fails to test properly. If you are waiting on a test, please check timestamps to verify that the test.log is moving at http://jenkins.bluematt.me/pull-tester/current/ Contact BlueMatt on freenode if something looks broken.
ACK