monzero-core.git/src/connectivity_tool, branch v0.9.2Monzero core node, command-line wallet, consensus code, and release tooling.
https://code.monzero.org/monzero-core.git/atom?h=v0.9.22016-03-11T16:17:08ZNeed to link boost::chrono in more places now2016-03-11T16:17:08ZHoward Chuhyc@symas.com2016-03-11T16:16:39Zurn:sha1:66c2fc7b7012acb48bae34cb0f5dd075cc56141dmove g_test_dbg_lock_sleep from a global to a function level static2016-02-22T19:34:09Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2016-02-22T19:34:09Zurn:sha1:5e3557d2c30f9f1a206d93441897793a993f3618
This avoids the need to define that variable in every program
which uses epee.
updated copyright year2015-12-31T06:39:56ZRiccardo Spagniric@spagni.net2015-12-31T06:39:56Zurn:sha1:de0392685063d93dbdad3a6b1a2712eaf94dd51a2014 network limit 1.2 +utils +toc -doc -drmonero2015-02-20T21:28:03Zrfree2monerorfreemonero@op.pl2015-02-20T21:28:03Zurn:sha1:ae2a50659f7dc74a5446a0dc3a5f8f78563b9e1f
new update of the pr with network limits
more debug options:
discarding downloaded blocks all or after given height.
trying to trigger the locking errors.
debug levels polished/tuned to sane values.
debug/logging improved.
warning: this pr should be correct code, but it could make
an existing (in master version) locking error appear more often.
it's a race on the list (map) of peers, e.g. between closing/deleting
them versus working on them in net-limit sleep in sending chunk.
the bug is not in this code/this pr, but in the master version.
the locking problem of master will be fixed in other pr.
problem is ub, and in practice is seems to usually cause program abort
(tested on debian stable with updated gcc). see --help for option
to add sleep to trigger the error faster.
year updated in license2015-01-02T16:52:46ZRiccardo Spagniric@spagni.net2015-01-02T16:52:46Zurn:sha1:f4b69d553a249ace3694e3b4fd307ddffa156d7dcmake: support 2.8.72014-10-24T19:29:51ZBen Boeckelben.boeckel@kitware.com2014-10-24T18:48:14Zurn:sha1:7d708e422397fb0ba8ac29855eb27964115e7217
Older versions of CMake support LINK_{PUBLIC,PRIVATE} while newer
versions prefer PUBLIC and PRIVATE instead, but still support the LINK_
prefix.
cmake: handle private vs. public headers2014-10-23T20:42:34ZBen Boeckelben.boeckel@kitware.com2014-10-21T16:38:00Zurn:sha1:f53f04724c714a40c10e8c0afdca465054fabca8cmake: refactor common code with executables2014-10-23T20:42:34ZBen Boeckelben.boeckel@kitware.com2014-10-21T15:21:28Zurn:sha1:c773f465ca7e691b94394d8c7c682c8eb78e5c25cmake: put each library into its own directory2014-10-23T20:42:34ZBen Boeckelben.boeckel@kitware.com2014-10-21T15:13:59Zurn:sha1:89cff7bddc6f76ae7382e92569f9a902b262cc5f
This cleans up the CMake code and shows patterns more easily (to be
refactored in the next commit).
Reorganize testnet constants2014-09-15T13:53:10ZZachary Michaelsmikezackles@gmail.com2014-09-05T02:14:36Zurn:sha1:fb4146fa343399229c754331ecc78fe0c759ec7c