forked from cerc-io/plugeth
3d57e377a4
- follow up locks and fix them - chainManager: call SetQueued for parentErr future blocks, uncomment TD checks, unskip test - make ErrIncorrectTD non-fatal to be forgiving to genuine mistaken nodes (temp) but demote them to guard against stuck best peers. - add purging to bounded nodeCache (config nodeCacheSize) - use nodeCache when creating blockpool entries and let non-best peers add blocks (performance boost) - minor error in addError - reduce idleBestPeerTimeout to 1 minute - correct status counts and unskip status passing status test - glogified logging
45 lines
1.3 KiB
Plaintext
45 lines
1.3 KiB
Plaintext
glog
|
|
====
|
|
|
|
Leveled execution logs for Go.
|
|
|
|
This is an efficient pure Go implementation of leveled logs in the
|
|
manner of the open source C++ package
|
|
http://code.google.com/p/google-glog
|
|
|
|
By binding methods to booleans it is possible to use the log package
|
|
without paying the expense of evaluating the arguments to the log.
|
|
Through the -vmodule flag, the package also provides fine-grained
|
|
control over logging at the file level.
|
|
|
|
The comment from glog.go introduces the ideas:
|
|
|
|
Package glog implements logging analogous to the Google-internal
|
|
C++ INFO/ERROR/V setup. It provides functions Info, Warning,
|
|
Error, Fatal, plus formatting variants such as Infof. It
|
|
also provides V-style logging controlled by the -v and
|
|
-vmodule=file=2 flags.
|
|
|
|
Basic examples:
|
|
|
|
glog.Info("Prepare to repel boarders")
|
|
|
|
glog.Fatalf("Initialization failed: %s", err)
|
|
|
|
See the documentation for the V function for an explanation
|
|
of these examples:
|
|
|
|
if glog.V(2) {
|
|
glog.Info("Starting transaction...")
|
|
}
|
|
|
|
glog.V(2).Infoln("Processed", nItems, "elements")
|
|
|
|
|
|
The repository contains an open source version of the log package
|
|
used inside Google. The master copy of the source lives inside
|
|
Google, not here. The code in this repo is for export only and is not itself
|
|
under development. Feature requests will be ignored.
|
|
|
|
Send bug reports to golang-nuts@googlegroups.com.
|