-
Hello.
I have took this code from example and substitite standard logger to logrus but if failes with message:
_Failed to write to log, *mpb.Progress instance can't be reused after *mpb.Progress.…
-
__Use case:__
Logrus version 1.9.0 has an open CVE. Repositories which host influx and scan for CVEs flag this dependency as the finding has been open for a very long time (10 months). Updating the…
-
# Problem and Background
"we found our logrus logger is responsible for large REST API slowdown every time new blocks arrives or accounts are written"
Logrus is well known to be slow compared to…
-
In the current repository there is a dependency called **logrus** and it is imported from [github.com/Sirupsen/logrus](github.com/Sirupsen/logrus)
However, according to [logrus documentation](https…
-
-
**Description**
I just started writing a small utility about images management
My import section in ly main.go looks like :
```
import (
"github.com/docker/docker/daemon/config"
"github.…
nikk0 updated
2 months ago
-
By default, logrus outputs to stderr. When running in GCE with the Stackdriver agent, stderr lines end up with severity 'warning', even when the level in the text-format is 'Info'.
As the [logrus r…
-
**Actual behavior**
When passing in `--log-timestamp=false` with either `--log-format=text|color` set, timestamps still get logged.
**Expected behavior**
No timestamps should get logged
**To R…
-
Please see https://github.com/grafana/k6/issues/2958
After some investigation, it seems like it won't be that difficult to get rid of the [`*logrus.Logger`](https://pkg.go.dev/github.com/sirupsen/l…
-
Clean up logrus output to limit the noise in the logs (such as the `[INFO]` and timestamp data)