monzero-core.git/src/blockchain_db/lmdb, branch v0.10.1Monzero core node, command-line wallet, consensus code, and release tooling.
https://code.monzero.org/monzero-core.git/atom?h=v0.10.12016-12-01T14:31:40Zdb_lmdb: add info in an error message when we can't get an output2016-12-01T14:31:40Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2016-12-01T14:31:40Zurn:sha1:0e18f4652200bbfd1173ad44f9766b9740a75524
Will be useful to debug
db_lmdb: guard against going out of sync on unexpected db results2016-12-01T14:29:35Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2016-12-01T14:29:35Zurn:sha1:c96f9b0255dc8b62055a693a24bfdc8e1b6e1b90
m_num_outputs keeps track of the number of outputs, which should
be the same as the size of both the output_txs and output_amounts
databases. If one goes out of sync, we need to throw to abort
whatever it is we were doing.
db_lmdb: minor pedantic tweaks2016-12-01T14:28:09Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2016-12-01T14:28:09Zurn:sha1:bef51e677e4338291b03eb32a34731c445678be0
Add consts in a few places where it makes sense, avoid unnecessary
memory reallocation where we know the full size needed at the outset,
simplify and avoid memory copy.
db_lmdb: set same packing format for output_data_t and pre_rct_output_data_t2016-12-01T14:26:18Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2016-12-01T14:26:18Zurn:sha1:3465c4ebc7d38b9825e2bc95a9279de7f03e7594
For safety, though it seems to have been the case already.
Also add a comment about the necessary layout identity.
wallet: select part of the fake outs from recent outputs2016-10-15T17:17:16Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2016-09-17T14:45:51Zurn:sha1:88faec75fe768a5702c3f8d9384c0913e4af22aa
25% of the outputs are selected from the last 5 days (if possible),
in order to avoid the common case of sending recently received
outputs again. 25% and 5 days are subject to review later, since
it's just a wallet level change.
Merge pull request #11282016-09-29T20:16:15ZRiccardo Spagniric@spagni.net2016-09-29T20:16:15Zurn:sha1:995dde4f950ced36a9630c6754e9b9e9fe261b3d
d2e11f3 db_lmdb: do not error if dropping a non existent hard fork table (moneromooo-monero)
db_lmdb: do not error if dropping a non existent hard fork table2016-09-24T15:15:50Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2016-09-24T15:15:50Zurn:sha1:d2e11f374a191f8331c65e30f2b623a44b8668deFix minor typo in "need resize" message.2016-09-21T19:40:07ZMyaguiandre@crespolopes.com2016-09-21T19:40:07Zurn:sha1:12427dd8d3721b0ab64e6a78881a18c49e15c931
Message observed while synchronizing a node from scratch.
"LMDB memory map needs resized"
Proposing a change to:
"LMDB memory map needs to be resized"core: faster find_blockchain_supplement2016-08-31T09:03:32Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2016-08-30T15:39:33Zurn:sha1:6cf8ca2a7f3e11ca5559018dfc9b20869c07cdce
Since this queries block heights for blocks that may or may not
exist, queries for non existing blocks would throw an exception,
and that would slow down the loop a lot. 7 seconds to go through
a 30 hash list.
Fix this by adding an optional return block height to block_exists
and using this instead. Actual errors will still throw an
exception.
This also cuts down on log exception spam.
db_lmdb: fix reorg with "halfway rct" coinbase outputs2016-08-29T21:44:17Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2016-08-29T21:44:17Zurn:sha1:1cdba42a77f7dfae3028c4bf106e247ea7c033fd