<feed xmlns='http://www.w3.org/2005/Atom'>
<title>monzero-core.git/src/blockchain_utilities/bootstrap_file.cpp, branch crash-pl</title>
<subtitle>Monzero core node, command-line wallet, consensus code, and release tooling.
</subtitle>
<id>https://code.monzero.org/monzero-core.git/atom?h=crash-pl</id>
<link rel='self' href='https://code.monzero.org/monzero-core.git/atom?h=crash-pl'/>
<link rel='alternate' type='text/html' href='https://code.monzero.org/monzero-core.git/'/>
<updated>2018-01-26T15:03:20Z</updated>
<entry>
<title>Update 2018 copyright</title>
<updated>2018-01-26T15:03:20Z</updated>
<author>
<name>xmr-eric</name>
<email>eric@moneroeric.com</email>
</author>
<published>2018-01-07T05:05:16Z</published>
<link rel='alternate' type='text/html' href='https://code.monzero.org/monzero-core.git/commit/?id=18216f19dd479466cb7fd38f52d23bddfcfd4880'/>
<id>urn:sha1:18216f19dd479466cb7fd38f52d23bddfcfd4880</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Merge pull request #2778</title>
<updated>2017-11-15T09:40:38Z</updated>
<author>
<name>Riccardo Spagni</name>
<email>ric@spagni.net</email>
</author>
<published>2017-11-15T09:40:38Z</published>
<link rel='alternate' type='text/html' href='https://code.monzero.org/monzero-core.git/commit/?id=cd070874bf2f9c9579028f70b936e9709b73dd68'/>
<id>urn:sha1:cd070874bf2f9c9579028f70b936e9709b73dd68</id>
<content type='text'>
c957795b fix output_stream_header memory leak (MaxXor)
</content>
</entry>
<entry>
<title>remove "using namespace std" from headers</title>
<updated>2017-11-14T16:56:10Z</updated>
<author>
<name>moneromooo-monero</name>
<email>moneromooo-monero@users.noreply.github.com</email>
</author>
<published>2017-10-10T14:47:08Z</published>
<link rel='alternate' type='text/html' href='https://code.monzero.org/monzero-core.git/commit/?id=383ff4f68943c5d998fba8caa20aee481583f214'/>
<id>urn:sha1:383ff4f68943c5d998fba8caa20aee481583f214</id>
<content type='text'>
It's nasty, and actually breaks on Solaris, where if.h fails to
build due to:

  struct map *if_memmap;
</content>
</entry>
<entry>
<title>fix output_stream_header memory leak</title>
<updated>2017-11-08T18:59:09Z</updated>
<author>
<name>MaxXor</name>
<email>admin@maxxor.org</email>
</author>
<published>2017-11-08T18:59:09Z</published>
<link rel='alternate' type='text/html' href='https://code.monzero.org/monzero-core.git/commit/?id=c957795bfae2ead9e2756cfcd86b3b65d0660d83'/>
<id>urn:sha1:c957795bfae2ead9e2756cfcd86b3b65d0660d83</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Use actual batch size for resize estimates</title>
<updated>2017-09-17T21:08:40Z</updated>
<author>
<name>Howard Chu</name>
<email>hyc@symas.com</email>
</author>
<published>2017-09-16T23:12:42Z</published>
<link rel='alternate' type='text/html' href='https://code.monzero.org/monzero-core.git/commit/?id=d2d8a41c47b408df35d1379255fc009f50a0b770'/>
<id>urn:sha1:d2d8a41c47b408df35d1379255fc009f50a0b770</id>
<content type='text'>
And optimize import startup:

Remember start_height position during initial count_blocks pass
to avoid having to reread entire file again to arrive at start_height
</content>
</entry>
<entry>
<title>blockchain_import: warn for chunks over 500000, not 100000</title>
<updated>2017-09-01T21:48:33Z</updated>
<author>
<name>moneromooo-monero</name>
<email>moneromooo-monero@users.noreply.github.com</email>
</author>
<published>2017-09-01T11:00:25Z</published>
<link rel='alternate' type='text/html' href='https://code.monzero.org/monzero-core.git/commit/?id=4e0e4e9942074609aa5c5cb44b8509a11b24bc4c'/>
<id>urn:sha1:4e0e4e9942074609aa5c5cb44b8509a11b24bc4c</id>
<content type='text'>
We have a lot of 350000 byte blocks now.
</content>
</entry>
<entry>
<title>update copyright year, fix occasional lack of newline at line end</title>
<updated>2017-02-21T17:38:18Z</updated>
<author>
<name>Riccardo Spagni</name>
<email>ric@spagni.net</email>
</author>
<published>2017-02-21T17:38:18Z</published>
<link rel='alternate' type='text/html' href='https://code.monzero.org/monzero-core.git/commit/?id=c3599fa7b94764d8f1cf7828a3f3a46067efe359'/>
<id>urn:sha1:c3599fa7b94764d8f1cf7828a3f3a46067efe359</id>
<content type='text'>
</content>
</entry>
<entry>
<title>tools: set requested log level</title>
<updated>2017-02-12T18:48:39Z</updated>
<author>
<name>moneromooo-monero</name>
<email>moneromooo-monero@users.noreply.github.com</email>
</author>
<published>2017-02-12T18:35:54Z</published>
<link rel='alternate' type='text/html' href='https://code.monzero.org/monzero-core.git/commit/?id=142e5e1eb47812c04a7623de7a8821726a1f1789'/>
<id>urn:sha1:142e5e1eb47812c04a7623de7a8821726a1f1789</id>
<content type='text'>
also move a couple logs from INFO to DEBUG
</content>
</entry>
<entry>
<title>Change logging to easylogging++</title>
<updated>2017-01-16T00:25:46Z</updated>
<author>
<name>moneromooo-monero</name>
<email>moneromooo-monero@users.noreply.github.com</email>
</author>
<published>2017-01-01T16:34:23Z</published>
<link rel='alternate' type='text/html' href='https://code.monzero.org/monzero-core.git/commit/?id=5833d66f6540e7b34e10ddef37c2b67bd501994b'/>
<id>urn:sha1:5833d66f6540e7b34e10ddef37c2b67bd501994b</id>
<content type='text'>
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.
</content>
</entry>
<entry>
<title>remove original Cryptonote blockchain_storage blockchain format</title>
<updated>2016-08-28T20:27:32Z</updated>
<author>
<name>moneromooo-monero</name>
<email>moneromooo-monero@users.noreply.github.com</email>
</author>
<published>2016-05-26T20:48:18Z</published>
<link rel='alternate' type='text/html' href='https://code.monzero.org/monzero-core.git/commit/?id=9e82b694da120708652871b55f639d1ef306a7ec'/>
<id>urn:sha1:9e82b694da120708652871b55f639d1ef306a7ec</id>
<content type='text'>
</content>
</entry>
</feed>
