Recordsgolanggithub.com/sirupsen/logrusfailure issue
Failure signature
PROJECT_COMPILE exit 1 ×1
<path> undefined: config.NewConfig
Evidence quality: complete · go/compiler · compiler-diagnostic · outer go run · First recorded: 2026-08-31 · Last seen: 2026-08-31
sha256:0a43185f3587…
github.com/sirupsen/logrus.New
Where it was measured
PASS means the release recorded a passing observation at PROJECT_COMPILE and no record of this failure. That is the nearest thing to absence this network can report, not a proof of it.
Where it reproduced
- os=linux · runtime=go@1.26 ×1 2026-08-31 → 2026-08-31
Nearest known PASS/FAIL boundaries
No release either side of this failure recorded a passing observation at this stage, so where it starts and stops is not established.
Dependency versions across releases
What each release of this package resolved its children to. A child whose version moved is listed first: that is where an upgrade changed something underneath you.
| Library | v1.9.3 | v1.8.1 | v1.6.0 | v1.4.2 |
|---|---|---|---|---|
| github.com/konsorten/go-windows-terminal-sequences | — | — | v1.0.3 | v1.0.1 |
| github.com/stretchr/testify | v1.7.0 | — | v1.2.2 | v1.8.1 |
| golang.org/x/sys | v0.31.0 | — | v0.47.0 | v0.18.0 |
Moved: 3 · unchanged at every release: 0
An edge records that a resolver placed one release beside another on a real machine. It is not a claim that the two work together; that question is answered by samples and contracts, not by presence here.
Evidence gaps
- No release in this window recorded a passing observation at PROJECT_COMPILE.
- Releases in this window never measured at PROJECT_COMPILE: 3
- No failure domain was inferred for this failure.
Published answers for the affected releases
- github.com/sirupsen/logrus v1.8.1 This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOW MIT-0 · 2026-08-27