-
-
Notifications
You must be signed in to change notification settings - Fork 3.1k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Change logging #55
Comments
This is quite related to the work @perfmode is doing in #66, updating for reference |
How does go-logging compare to glog? |
glog looks pretty nice. I like the 'V' feature it has. One thing i like better about go-logging is the ability to set different logging levels per module. i.e. when debugging the dht, you can set all dht logging levels on, but turn ones related to other package off (or at least to Error only) |
That's really useful— On Sun, Sep 21, 2014 at 11:33 AM, Jeromy Johnson notifications@github.com
|
closing as we are using almost exclusively go-logging now |
…/multiformats/go-multiaddr-0.1.2 Bump github.com/multiformats/go-multiaddr from 0.1.1 to 0.1.2
…dules/github.com/multiformats/go-multiaddr-0.1.2 Bump github.com/multiformats/go-multiaddr from 0.1.1 to 0.1.2
I would like to update all the logging in ipfs (util.DOut, and friends) to instead use go-logging. This will help us out immensely once we start doing larger deloys and things start failing.
The text was updated successfully, but these errors were encountered: