Monzero core node, command-line wallet, consensus code, and release tooling. https://code.monzero.org/monzero-core.git/atom?h=v0.12.2.0 2018-01-26T15:03:20Z 2018-01-26T15:03:20Z xmr-eric eric@moneroeric.com 2018-01-07T05:05:16Z urn:sha1:18216f19dd479466cb7fd38f52d23bddfcfd4880 2017-12-16T23:28:43Z moneromooo-monero moneromooo-monero@users.noreply.github.com 2017-11-29T19:30:06Z urn:sha1:bb89ae8b2058d98a764f24e17e6c58089dd548f0 These even had the epee namespace. This fixes some ugly circular dependencies. 2017-11-28T20:18:01Z rbrunner7 rbrunner@dreamshare.ch 2017-11-26T14:26:17Z urn:sha1:cf5f62361682877a08b246a0d04827c5c4cc30f5 Deleted 3 out of 4 calls to method connection_basic::sleep_before_packet that were erroneous / superfluous, which enabled the elimination of a "fudge" factor of 2.1 in connection_basic::set_rate_up_limit; also ended the multiplying of limit values and numbers of bytes transferred by 1024 before handing them over to the global throttle objects 2017-08-07T13:24:58Z Riccardo Spagni ric@spagni.net 2017-08-07T13:24:58Z urn:sha1:6db8a60a18c3678824016234b2153b4b0f0dbbdd 158c3ecf core: thread most of handle_incoming_tx (moneromooo-monero) f57ee382 cryptonote_protocol: retry stale spans early (moneromooo-monero) 90df52e1 cryptonote_protocol: light cleanup (moneromooo-monero) 84e23156 cryptonote_protocol: avoid spurious SYNCHRONIZED OK messages (moneromooo-monero) 5be43fcd cryptonote_protocol_handler: sync speedup (moneromooo-monero) 2017-08-07T08:33:14Z moneromooo-monero moneromooo-monero@users.noreply.github.com 2017-07-08T16:59:39Z urn:sha1:90df52e12f4fbf40cb475670f1d325e03abbf327 2017-07-31T15:36:52Z moneromooo-monero moneromooo-monero@users.noreply.github.com 2017-07-31T15:36:52Z urn:sha1:214fd81e9362f183603bacdb671e06192dcb5808 2017-02-25T12:10:29Z moneromooo-monero moneromooo-monero@users.noreply.github.com 2017-02-25T12:10:29Z urn:sha1:96ce57d5514165f83d147628474ab68dbe4f022a it scares users 2017-02-21T17:38:18Z Riccardo Spagni ric@spagni.net 2017-02-21T17:38:18Z urn:sha1:c3599fa7b94764d8f1cf7828a3f3a46067efe359 2017-01-22T22:31:34Z Miguel Herranz miguel@ipglider.org 2017-01-22T22:31:34Z urn:sha1:0644eed7728d3b5146ca7b53f7c50a56b02b327b 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.