go-log
go-log copied to clipboard
A logging library used by go-ipfs
Bumps [golang.org/x/sys](https://github.com/golang/sys) from 0.0.0-20210630005230-0f9fa26af87c to 0.1.0. Commits See full diff in compare view [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter...
Attempt to resolve #139
It would be nice to be able to annotate the logger's name after it is instantiated.
Introduction 👋 --- If I want to change the logging output from `Stderr` to `Stdout`, the os env `GOLOG_OUTPUT` should be changed to `stdout` Still, after setting env to only...
If the user only wants to see the log output to be in stdout with no stderr, then this can be a fix without making `GOLOG_FILE = /dev/null`
@arajasek just pushed a release tag: v2.5.1. Please manually verify validity (using [`gorelease`](https://pkg.go.dev/golang.org/x/exp/cmd/gorelease)), and update `version.json` to reflect the manually released version, if necessary. In the future, please use the...
There is a legitimate use-case to be able to examine the result of `configFromEnv` from an external caller. See discussion here for details: https://github.com/filecoin-project/lotus/pull/6743#discussion_r668728046
- `SetLogLevel` has a special case for `*`, yet `SetAllLoggers` exists. - `SetLogLevel` takes `level` as a `string`, instead of a `"github.com/whyrusleeping/go-logging".Level`.
It would be awesome if `ipfs log tail` could subscribe to a specific subsystem (or set thereof) at a specific log level, without setting that level globally). To do this,...
The default zap file backend logging backend is really dumb and doesn't have any internal buffering. We need to: 1. Buffer writes. 2. Drop log messages when the buffer is...