cryptocode

``` [ RUN ] wallet.select_account /workspace/rai/qt_test/qt.cpp:96: Failure Value of: key4 Actual: 32-byte object Expected: key2 Which is: 32-byte object [ FAILED ] wallet.select_account (55 ms) ``` **FIXED**

node.unlock_search fails sporadically. When debugging it this sequence happens: `vote_generator::send -> foreach_representative -> wallet.store.fetch` ...where fetch returns an error here: ``` if (!result) { nano::public_key compare (nano::pub_key (prv.data)); std::cout

``` [ RUN ] wallet.no_work Expected equality of these values: 0 cached_work Which is: 4545208490332381752 ``` Happened once, unable to reproduce **FIXED**

``` [ RUN ] work.eco_pow work_pool.cpp:185: Failure Expected: (future1.get ()) < (future2.get ()), actual: 8-byte object vs 8-byte object ``` **FIXED**

``` [==========] Running 1 test from 1 test case. [----------] Global test environment set-up. [----------] 1 test from active_transactions [ RUN ] active_transactions.adjusted_difficulty_priority nano/core_test/active_transactions.cpp:143: Failure Expected: (i->adjusted_difficulty) < (last_adjusted), actual:...

``` [ RUN ] ledger.unchecked_epoch_invalid core_test/ledger.cpp:2580: Failure Value of: node1.active.empty () Actual: false Expected: true ``` **FIXED**

``` [ RUN ] active_transactions.prioritize_chains nano/core_test/active_transactions.cpp:211: Failure Value of: system.poll () Actual: Deadline expired Expected: ``` **FIXED**

`confirmation_height.modified_chain` sometimes get stuck (no timeout), presumably it's one of the `while (!node->write_database_queue.contains (nano::writer::confirmation_height))` loops @wezrule ? **FIXED** (was reproducible, but now survives thousands of iterations, so seems fixed by...

Thanks for testing the WebSockets feature and initiating the discussion! The possibility of using it as an RPC came up earlier. Given the full duplex nature of WS we'd need...

From the source code/docs: MDB_PAGE_FULL - there is insufficient room in the page. This error should never happen since all callers already calculate the page's free space before calling this...