Monzero core node, command-line wallet, consensus code, and release tooling. https://code.monzero.org/monzero-core.git/atom?h=v0.10.2 2017-02-21T17:38:18Z 2017-02-21T17:38:18Z Riccardo Spagni ric@spagni.net 2017-02-21T17:38:18Z urn:sha1:c3599fa7b94764d8f1cf7828a3f3a46067efe359 2017-02-21T15:11:12Z Riccardo Spagni ric@spagni.net 2017-02-21T15:11:12Z urn:sha1:058eed369ba328dce34e9c1593a9ddbfaceea2af 2017-02-20T22:58:16Z moneromooo-monero moneromooo-monero@users.noreply.github.com 2017-02-18T16:30:29Z urn:sha1:f640512c53caca9d7c3c69802841d174818cf953 It just checks and prints a message if there is a new version for now. 2017-02-12T21:20:27Z Riccardo Spagni ric@spagni.net 2017-02-12T21:20:27Z urn:sha1:c64e10c2d7709c6ae2ebc1fd5e4e3440add7f47f 73785263 backtrace_symbols() requires -lexecinfo on dragonflybsd (Dan Miller) 2017-02-09T19:22:12Z Dan Miller pigeons 2017-02-08T22:50:14Z urn:sha1:737852639393033c33be171a5d096114bd975b64 freebsd also needs -lexecinfo for backtrace() 2017-02-08T13:45:15Z kenshi84 kenshi84@protonmail.ch 2017-01-26T15:07:23Z urn:sha1:8027ce0c75f882de0523e668defa0bc3c8564e96 2017-02-05T03:33:33Z MoroccanMalinois MoroccanMalinois@protonmail.com 2017-01-21T04:15:00Z urn:sha1:c833a39a4d48784a2e9f1d3d2f604ffd5a9b5f07 2017-02-04T12:33:03Z moneromooo-monero moneromooo-monero@users.noreply.github.com 2017-02-04T12:33:03Z urn:sha1:cd34fc655d5bf4ed5d9425222b78a771b7a55294 This avoids using libunwind, which often causes trouble. 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. 2017-01-16T00:01:08Z Riccardo Spagni ric@spagni.net 2017-01-16T00:01:08Z urn:sha1:ec323d8c3f61c3ca86d1ef2b604d4dd75c59e250 d561f4ad enable clang checks that were disabled (Chris Vickio) 0aefb2f6 remove std::move from return statements (pessimizing-move warning) (Chris Vickio) 629d5b76 change counter from bool to int (deprecated-increment-bool warning) (Chris Vickio) fb76d439 add extra braces around subobjects (missing-braces warning) (Chris Vickio) 3b6d5f25 make struct/class declarations consistent (mismatched-tags warning) (Chris Vickio) fcf66925 remove unused fields from network_throttle (unused-private-field warning) (Chris Vickio) 296f8c16 inline unused function (for unused-function warning) (Chris Vickio)