Tags: sirupsen/logrus
Tags
v1.10.2 This is a small maintenance release that updates `github.com/stretchr/testify` to v1.12.1, removing the legacy `gopkg.in/yaml.v3` dependency from Logrus' dependency graph. There are no functional changes in this release. Dependency Changes: - update github.com/stretchr/testify to v1.12.1
v1.10.1 This patch release fixes two issues in field formatting and handling: - Fix a regression introduced in v1.10.0 where `TextFormatter` could panic when formatting nil or panicking `error` and `fmt.Stringer` values. - Allow function-backed values implementing `error` to be used with `WithError`, `WithField`, and `WithFields`. Dependency Changes - update github.com/stretchr/testify to v1.12.0
v1.10.0 Notable changes: - Add bidirectional `log/slog` integration with a Logrus hook and `slog.Handler`. - Add minimal, composable logging interfaces for individual log levels. - Fix reentrant logging deadlocks and improve concurrency safety around formatters, hooks, and entries. - Fix generic `Log`, `Logf`, `Logln`, and `LogFn` methods unexpectedly panicking at `PanicLevel`. - Allow `Entry.Caller` to be set explicitly and preserved across derived entries. - Improve `TextFormatter` performance and reduce allocations significantly. - Improve common Logger and Entry hot paths and caller-reporting performance. - Update `TextFormatter` handling for `[]byte`, debug/trace colors, and Windows ANSI terminals. - Raise the minimum supported Go version to Go 1.23. - Deprecate `Entry.HasCaller` and `MutexWrap`.
v1.9.4 Notable changes: - go.mod: update minimum supported go version to v1.17. - go.mod: bump up dependencies. - Touch-up godoc and add "doc" links. - README: fix links, grammar, and update examples. - Add GNU/Hurd support. - Add WASI wasip1 support. - Remove uses of deprecated `ioutil` package. - CI: update actions and golangci-lint. - CI: remove appveyor, add macOS.
fix panic in Writer Commit 766cfec introduced this bug by defining an incorrect split function. First it breaks the old behavior because it never splits at newlines now. Second, it causes a panic because it never tells the scanner to stop. See the bufio.ScanLines function, something like: ``` if atEOF && len(data) == 0 { return 0, nil, nil } ``` is needed to do that. This commit fixes it by restoring the old behavior and calling bufio.ScanLines but also keep the 64KB check in place to avoid buffering for to long. Two tests are added to ensure it is working as expected. Fixes #1383 Signed-off-by: Paul Holzinger <pholzing@redhat.com>
PreviousNext