aboutsummaryrefslogtreecommitdiff
path: root/contrib/epee/include/storages/levin_abstract_invoke2.h (follow)
AgeCommit message (Collapse)AuthorFilesLines
2022-04-18Trimming FatJeffrey1-48/+0
Remove unused include statements or unused definitions.
2021-01-19Remove payload copy in all outgoing p2p messagesLee Clagett1-33/+22
2021-04-16Revert "Merge pull request #7136"luigi11111-22/+33
This reverts commit 63c7ca07fba2f063c760f786a986fb3e02fb040e, reversing changes made to 2218e23e84a89e9a1e4c0be5d50f891ab836754f.
2021-01-16Remove payload copy in all outgoing p2p messagesLee Clagett1-33/+22
2021-01-07storages: overridable limits for loading portable_storage from binarymoneromooo-monero1-5/+10
2020-10-10Change epee binary output from std::stringstream to byte_streamLee Clagett1-14/+17
2020-08-02epee: further defending against exceptions in command handlersmoneromooo-monero1-0/+7
2020-05-31Fix boost <1.60 compilation and fix boost 1.73+ warningsLee Clagett1-4/+5
2020-05-14build: fix boost 1.73 compatibilityselsta1-4/+4
2020-01-26network: log traffic and add a simple traffic analysis scriptmoneromooo-monero1-5/+43
2018-12-23epee: better network buffer data structuremoneromooo-monero1-10/+11
avoids pointless allocs and memcpy
2018-02-02pass large parameters by const ref, not valuemoneromooo-monero1-1/+1
Coverity 136394 136397 136409 136526 136529 136533 175302
2017-12-27epee: check some error return valuesmoneromooo-monero1-8/+18
2017-08-05epee: remove a couple unused localsmoneromooo-monero1-2/+2
2017-01-16Change logging to easylogging++moneromooo-monero1-2/+5
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
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
2014-07-25move modified epee code to new classes, revert licensefluffypony1-25/+21
2014-07-23License updated to BSD 3-clausefluffypony1-21/+25
2014-03-03moved all stuff to githubAntonio Juarez1-0/+289