-
All instances of Sirupsen/logrus in Go code need to be renamed to sirupsen/logrus. Please see [this comment](https://github.com/sirupsen/logrus/issues/570#issuecomment-313933276) for more information …
akutz updated
6 years ago
-
### Current Behavior
Structured logging has now been standardized in the `log/slog` package. API consumers that use slog need to allocate a separate logrus logger to use with regclient, which i…
-
We need to keep all interactions. That includes the coverage files we are collecting.
-
https://github.com/sirupsen/logrus/issues/959
https://github.com/sirupsen/logrus/pull/977
-
Hello,
particularly I have the issue with the following line in application.go:
~~~go
fmt.Println("state", status.PlayerState, "status.Idle
Reason", status.IdleReason)
~~~
The output itsel…
-
In our codebase, we have 2 to 3 instances of TiKV in certain circumstances. All of them are currently logging through the `logrus` standard logger.
It would be preferable if each tikv-client instan…
-
**Describe the bug**
It is not a bug report but an attempt to warn on harm from code of logrus logger hook. https://github.com/elastic/apm-agent-go/blob/main/module/apmlogrus/hook.go In our case, thi…
-
## Expected Behavior
One of my nodes is emitting a warning about incompatible nft rules and then panic-looping while failing to log something.
## Current Behavior
```
2023-09-17 16:22:39…
-
can you please add a release ?
(for example release 1.0)
so other people can add constraints in the gopkg.toml files for 'dep ensure'?
Currently I'm using the last master revision as a dep cons…
-
It seems Logrus is more popular in go api application.