aboutsummaryrefslogtreecommitdiff
path: root/contrib/epee/include/storages (follow)
AgeCommit message (Collapse)AuthorFilesLines
2017-12-16move includes around to lessen overall loadmoneromooo-monero3-2/+5
2017-11-14epee: don't disable -Wtautological-constant-out-of-range-compare on GCCmoneromooo-monero1-0/+2
It's a CLANG only option, and causes GCC to error out
2017-10-28epee: disable a spurious warning for a storage functionmoneromooo-monero1-0/+1
2017-10-15Serializer: string to integer conversion for MyMonero compatibilityJaquee1-0/+27
mymonero timestamp conversion
2017-10-15epee http_client SSL supportJaquee1-1/+4
2017-08-15Merge pull request #2253Riccardo Spagni1-2/+2
51ebedb8 epee: remove a couple unused locals (moneromooo-monero)
2017-08-05epee: remove a couple unused localsmoneromooo-monero1-2/+2
2017-07-05Fix spelling errorsErik de Castro Lopo1-1/+1
2017-02-24Updated default RPC timeout from 5 seconds to 15 secondsLee Clagett1-4/+4
2017-02-06Add server auth to monerod, and client auth to wallet-cli and wallet-rpcLee Clagett1-4/+7
2017-01-25Updates to epee HTTP client codeLee Clagett1-17/+17
- http_simple_client now uses std::chrono for timeouts - http_simple_client accepts timeouts per connect / invoke call - shortened names of epee http invoke functions - invoke command functions only take relative path, connection is not automatically performed
2017-01-20removing some unsed epee filesmoneroexamples1-132/+0
2017-01-16Change logging to easylogging++moneromooo-monero2-4/+7
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-10-27Unkonown -> unknownNanoAkron1-1/+1
2016-05-18contrib: epee: add exception spec to throwing destructorsredfish1-1/+1
The destructors get a noexcept(true) spec by default, but these destructors in fact throw exceptions. An alternative fix might be to not throw (most if not all of these throws are non-essential error-reporting/logging).
2016-03-25remove unecessary and bad std::move from portable_storage_template_helper.hRiccardo Spagni1-2/+2
2016-03-21Revert "Print stack trace upon exceptions"moneromooo-monero1-2/+2
Ain't nobody got time for link/cmake skullduggery. This reverts commit fff238ec94ac6d45fc18c315d7bc590ddfaad63d.
2016-03-19Print stack trace upon exceptionsmoneromooo-monero1-2/+2
Useful for debugging users' logs
2015-05-25Fix compile for GCC 5.1.0warptangent1-1/+1
Add fix for compile error with multiple uses of peerid_type (uint64_t) variable in lambda expression. - known GCC issue: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65843 epee: replace return value of nullptr for expected boolean with false. Fixes #231.
2015-02-202014 network limit 1.1 +utils +toc -doc -drmonerorfree2monero1-2/+2
Update of the PR with network limits works very well for all speeds (but remember that low download speed can stop upload because we then slow down downloading of blockchain requests too) more debug options fixed pedantic warnings in our code should work again on Mac OS X and FreeBSD fixed warning about size_t tested on Debian, Ubuntu, Windows(testing now) TCP options and ToS (QoS) flag FIXED peer number limit FIXED some spikes in ingress/download FIXED problems when other up and down limit
2015-01-02year updated in licenseRiccardo Spagni10-10/+10
2014-07-25move modified epee code to new classes, revert licensefluffypony14-353/+316
2014-07-23License updated to BSD 3-clausefluffypony14-316/+353
2014-05-250.8.8updatemydesktop3-41/+53
2014-04-30mac osx building fixesmydesktop1-1/+1
2014-04-30various fixes to allow mac osx compilationmydesktop1-1/+1
2014-04-07Improvements in JSON RPCAntonio Juarez1-1/+17
2014-04-02json rpc for wallet and bugfixAntonio Juarez1-2/+2
2014-03-20some fixesAntonio Juarez1-1/+1
2014-03-03moved all stuff to githubAntonio Juarez14-0/+2893
generated by cgit v1.2.3 (git 2.25.1) at 2024-12-29 19:16:02 +0000