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-05-31T11:17:48Z 2018-05-31T11:17:48Z moneromooo-monero moneromooo-monero@users.noreply.github.com 2018-05-26T18:32:18Z urn:sha1:ca7f0249eb47efecf782c4325107514305278db8 It had not been updated to the function type change 2017-12-16T22:46:38Z moneromooo-monero moneromooo-monero@users.noreply.github.com 2017-11-25T22:25:05Z urn:sha1:09ce03d612e54231694eee2fb9e5c807b2bfc341 2017-11-26T09:37:37Z Cifrado hello@cifrado.me 2017-11-22T12:53:18Z urn:sha1:287dde63d8f67c56b08c67b7a93ef7e58a157be1 2017-08-22T07:30:04Z Howard Chu hyc@symas.com 2017-08-21T11:55:06Z urn:sha1:c088d38a57f6be5c8399a8c2243b2862d9f67cbe And don't use std::mutex 2017-08-02T13:44:42Z moneromooo-monero moneromooo-monero@users.noreply.github.com 2017-08-02T13:44:42Z urn:sha1:b7d6ec83648f145190cab9044d321f3ef6d4e8e7 Should help people who don't realize why they haven't seen their monero yet. 2017-07-09T13:50:04Z Jethro Grassie jtg@xtrabass.com 2017-07-07T19:40:32Z urn:sha1:6955976b2d3f25205fc9fd065744d69ba64cccfa - Add missing unbind key - Fix colored messages - Add command completion - Preserve last command input - Fix cursor position issues - Fix trailing whitespace in commands - Synchronize set_prompt 2017-06-24T11:34:56Z Jethro Grassie jtg@xtrabass.com 2017-06-20T13:22:55Z urn:sha1:fdccf7e6c3a90af62f4979b39227e8ac23f0ecbb Color prompt now working and no reprompting on exit command. 2017-06-18T14:08:37Z jethro jtg@xtrabass.com 2017-05-29T22:39:49Z urn:sha1:e1f3dfccc8a099eb08e0d9ef758b216d035afd78 This PR adds readline support to the daemon and monero-wallet-cli. Only GNU readline is supported (e.g. not libedit) and there are cmake checks to ensure this. There is a cmake variable, Readline_ROOT_DIR that can specify a directory to find readline, otherwise some default paths are searched. There is also a cmake option, USE_READLINE, that defaults to ON. If set to ON, if readline is not found, the build continues but without readline support. One negative side effect of using readline is that the color prompt in the wallet-cli now has no color and just uses terminal default. I know how to fix this but it's quite a big change so will tackle another time. 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-05T01:11:05Z MoroccanMalinois MoroccanMalinois@protonmail.com 2017-01-05T01:11:05Z urn:sha1:80abc3bc4a73f3ba6ffd40b1a03de0cc4d01e3c9