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-10T22:35:25Z Riccardo Spagni ric@spagni.net 2017-02-10T22:35:25Z urn:sha1:eacf2124b6822d088199179b18d4587404408e0f ce7fcbb4 Add server auth to monerod, and client auth to wallet-cli and wallet-rpc (Lee Clagett) 2017-02-08T13:45:15Z kenshi84 kenshi84@protonmail.ch 2017-01-26T15:07:23Z urn:sha1:8027ce0c75f882de0523e668defa0bc3c8564e96 2017-02-06T06:15:41Z Lee Clagett code@leeclagett.com 2017-02-05T22:48:03Z urn:sha1:ce7fcbb4aea884bb4bf433cf419ffa267f859c87 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-09-18T19:32:02Z moneromooo-monero moneromooo-monero@users.noreply.github.com 2016-09-07T20:38:41Z urn:sha1:eeb2bbc0fcc9c5afa2c3aa12915b4d3f31115e56 This is intended to catch traffic coming from a web browser, so we avoid issues with a web page sending a transfer RPC to the wallet. Requiring a particular user agent can act as a simple password scheme, while we wait for 0MQ and proper authentication to be merged. 2016-09-16T19:47:52Z moneromooo-monero moneromooo-monero@users.noreply.github.com 2016-09-16T19:47:52Z urn:sha1:423776f9b166606c1fec32908ddeb42badd4b4e7 Helps with investigating bug reports 2016-07-27T05:52:33Z redfish redfish@galactica.pw 2016-07-27T05:02:55Z urn:sha1:0f990d018357413d5eab36b361aa9236e6b8795d By default the flag is enabled whenever libunwind is found on the system, with the exception of static build on OSX (for which we can't install the throw hook #932 due to lack of support for --wrap in OSX ld64 linker). 2016-06-30T21:15:40Z moneromooo-monero moneromooo-monero@users.noreply.github.com 2016-06-30T21:15:40Z urn:sha1:459ec6040e95444a19de9cfbf34b5b9c94e09060 When an exception happens while reading the config file, we need to print the error, as the logging system isn't initialized yet, so the generic catch will not print anything. 2016-06-19T19:14:11Z Riccardo Spagni ric@spagni.net 2016-06-19T19:14:11Z urn:sha1:e97d96ccfbb639f621cc4f4336c54cc02fa43485 e409e59 Print stack trace on exceptions (moneromooo-monero) ef4ff42 connection_basic: avoid gratuitous exception (moneromooo-monero)