Recordsgolanggithub.com/spf13/viperfailure issue
Failure signature
PROJECT_TEST Evidence gap ×1
Evidence quality: legacy-evidence-incomplete · First recorded: 2026-09-08 · Last seen: 2026-09-08
viper.New viper.Viper.GetInt viper.Viper.GetString viper.Viper.MergeConfigMap viper.Viper.Set
Where it was measured
PASS means the release recorded a passing observation at PROJECT_TEST 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
- executionContext=go · os=linux · runtime=go@1.26 ×1 2026-09-08 → 2026-09-08
Nearest known PASS/FAIL boundaries
The two adjacent releases the verdict changes across. Releases nothing measured do not close the gap; they are counted instead.
-
Last passing release v1.7.0 → first failing release v1.21.0
What differs across the boundary
- github.com/bketelsen/crypt v0.0.3-0.20200106085610-5cbc8cc4026c → — hypothesis
- github.com/fsnotify/fsnotify v1.4.7 → v1.9.0 hypothesis
- github.com/go-viper/mapstructure/v2 — → v2.4.0 hypothesis
- github.com/hashicorp/hcl v1.0.0 → — hypothesis
- github.com/magiconair/properties v1.8.1 → — hypothesis
- github.com/mitchellh/mapstructure v1.1.2 → — hypothesis
- github.com/pelletier/go-toml v1.2.0 → — hypothesis
- github.com/pelletier/go-toml/v2 — → v2.2.4 hypothesis
- github.com/sagikazarmark/locafero — → v0.11.0 hypothesis
- github.com/spf13/afero v1.1.2 → v1.15.0 hypothesis
- github.com/spf13/cast v1.3.0 → v1.10.0 hypothesis
- github.com/spf13/jwalterweatherman v1.0.0 → — hypothesis
- github.com/spf13/pflag v1.0.3, v1.0.5 → v1.0.10 hypothesis
- github.com/stretchr/testify v1.3.0, v1.7.0 → v1.11.1 hypothesis
- github.com/subosito/gotenv v1.2.0 → v1.6.0 hypothesis
- go.yaml.in/yaml/v3 — → v3.0.4 hypothesis
- gopkg.in/ini.v1 v1.51.0 → — hypothesis
- gopkg.in/yaml.v2 v2.4.0 → — hypothesis
A version that moved across the boundary is a candidate, not a cause. Only a receipt that recorded the failure and the tree it resolved in the same run is marked as evidence.
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.
Moved: 8 · unchanged at every release: 11
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
- The evidence for this failure was not preserved, so it has no established cause. Its stored hash is provenance, not an identity.
- No failure domain was inferred for this failure.
Published answers for the affected releases
- github.com/spf13/viper v1.21.0: Prove Viper 1.21.0 multi-tier configuration precedence order (Set > Flag > Env > Config > Default), layer introspection with IsSet and InConfig, and MergeConfig map merging semantics 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. HOWviper.Newviper.Setviper.BindPFlagviper.AutomaticEnvviper.ReadConfigviper.MergeConfigviper.SetDefaultviper.IsSetviper.InConfiggo MIT-0 · 2026-08-17
- github.com/spf13/viper v1.21.0: Pin Viper 1.21.0 string-slice parsing differences across environment values, pflag StringSlice values, and in-memory YAML 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. HOWviper.GetStringSliceviper.Unmarshalviper.AutomaticEnvviper.SetEnvKeyReplacerviper.SetEnvPrefixviper.BindPFlagviper.ReadConfigviper.SetDefaultgo MIT-0 · 2026-08-17