Monzero core node, command-line wallet, consensus code, and release tooling. https://code.monzero.org/monzero-core.git/atom?h=crash-pl 2018-03-05T02:55:05Z 2018-03-05T02:55:05Z stoffu stoffu@protonmail.ch 2018-02-16T11:04:04Z urn:sha1:af773211cbc620a1be54f517bd60e587d58a7e93 2018-02-16T20:32:01Z whythat whythat@protonmail.com 2018-01-21T15:29:55Z urn:sha1:05a12ccc2dc920f4a997e66e6965ae60c1a4c65e 2018-01-26T15:03:20Z xmr-eric eric@moneroeric.com 2018-01-07T05:05:16Z urn:sha1:18216f19dd479466cb7fd38f52d23bddfcfd4880 2017-12-28T06:59:16Z Riccardo Spagni ric@spagni.net 2017-12-28T06:59:16Z urn:sha1:95a687d584f95170056e1e01c3bfb607cf5bc6c4 9e07ccf1 daemon: remove some superfluous includes (moneromooo-monero) 2017-12-17T10:28:39Z moneromooo-monero moneromooo-monero@users.noreply.github.com 2017-12-17T10:28:39Z urn:sha1:9e07ccf1f59b4544cedfc6753dbc0b8f87625d8d 2017-12-16T23:28:38Z moneromooo-monero moneromooo-monero@users.noreply.github.com 2017-11-29T22:53:58Z urn:sha1:4abf25f3c901016803515771cc19997d9a95bacb As a followon side effect, this makes a lot of inline code included only in particular cpp files (and instanciated when necessary. 2017-02-21T17:38:18Z Riccardo Spagni ric@spagni.net 2017-02-21T17:38:18Z urn:sha1:c3599fa7b94764d8f1cf7828a3f3a46067efe359 2017-02-21T15:06:07Z moneromooo-monero moneromooo-monero@users.noreply.github.com 2017-02-21T15:06:07Z urn:sha1:417b126fc420b7bac9a385f9576a5b80e840ee67 You're wondering how this fixes core tests, aren't you... It prevents the miner (initialized by cryptonote::core) from breaking trying to access arguments that were not added. Since the tests don't use the miner directly, it makes more sense to have cryptonote_core add those, since it also uses the miner. 2017-01-16T00:25:46Z moneromooo-monero moneromooo-monero@users.noreply.github.com 2017-01-01T16:34:23Z urn:sha1:5833d66f6540e7b34e10ddef37c2b67bd501994b This replaces the epee and data_loggers logging systems with a single one, and also adds filename:line and explicit severity levels. Categories may be defined, and logging severity set by category (or set of categories). epee style 0-4 log level maps to a sensible severity configuration. Log files now also rotate when reaching 100 MB. To select which logs to output, use the MONERO_LOGS environment variable, with a comma separated list of categories (globs are supported), with their requested severity level after a colon. If a log matches more than one such setting, the last one in the configuration string applies. A few examples: This one is (mostly) silent, only outputting fatal errors: MONERO_LOGS=*:FATAL This one is very verbose: MONERO_LOGS=*:TRACE This one is totally silent (logwise): MONERO_LOGS="" This one outputs all errors and warnings, except for the "verify" category, which prints just fatal errors (the verify category is used for logs about incoming transactions and blocks, and it is expected that some/many will fail to verify, hence we don't want the spam): MONERO_LOGS=*:WARNING,verify:FATAL Log levels are, in decreasing order of priority: FATAL, ERROR, WARNING, INFO, DEBUG, TRACE Subcategories may be added using prefixes and globs. This example will output net.p2p logs at the TRACE level, but all other net* logs only at INFO: MONERO_LOGS=*:ERROR,net*:INFO,net.p2p:TRACE Logs which are intended for the user (which Monero was using a lot through epee, but really isn't a nice way to go things) should use the "global" category. There are a few helper macros for using this category, eg: MGINFO("this shows up by default") or MGINFO_RED("this is red"), to try to keep a similar look and feel for now. Existing epee log macros still exist, and map to the new log levels, but since they're used as a "user facing" UI element as much as a logging system, they often don't map well to log severities (ie, a log level 0 log may be an error, or may be something we want the user to see, such as an important info). In those cases, I tried to use the new macros. In other cases, I left the existing macros in. When modifying logs, it is probably best to switch to the new macros with explicit levels. The --log-level options and set_log commands now also accept category settings, in addition to the epee style log levels. 2016-03-25T07:12:25Z Riccardo Spagni ric@spagni.net 2016-03-25T06:22:06Z urn:sha1:0d30b657859d6ebd3188bd16dfaa9c79c3dfcaa7 bfd4a28 Update BlockchainDB documentation (Thomas Winget) 797357e Change Doxyfile, Blockchain not blockchain_storage (Thomas Winget) c835215 remove defunct code from cryptonote::core (Thomas Winget) 50dba6d cryptonote::core doxygen documentation (Thomas Winget) 8ac329d doxygen documentation for difficulty functions (Thomas Winget) 540a76c Move checkpoint functions into checkpoints class (Thomas Winget) 1b0c98e doxygen documentation for checkpoints.{h,cpp} (Thomas Winget) 89c24ac Remove unnecessary or defunct code (Thomas Winget) ab0ed14 doxygen include private and static members (Thomas Winget) 3a48449 Updated documentation for blockchain.* (Thomas Winget)