In a project that has been running stably, occasional panic seems to be related to Viper. (However, after testing, all functions are normal and the panic cannot be reproduced through the tests for the time being.) #1978
Labels
kind/bug
Something isn't working
Preflight Checklist
Viper Version
1.19.0
Go Version
1.22.0
Config Source
Manual set
Format
JSON
Repl.it link
No response
Code reproducing the issue
Expected Behavior
I hope it can run stably.
Actual Behavior
panic: runtime error: invalid memory address or nil pointer dereference
[signal 0xc0000005 code=0x0 addr=0x68 pc=0x7ff65768aa0e]
goroutine 214013 [running]:
github.com/spf13/viper.(*Viper).getConfigFile(0x32?)
C:/Users/srackHall/go/pkg/mod/github.com/spf13/viper@v1.19.0/viper.go:2227 +0xe
github.com/spf13/viper.(*Viper).WatchConfig.func1()
C:/Users/srackHall/go/pkg/mod/github.com/spf13/viper@v1.19.0/viper.go:450 +0xf9
created by github.com/spf13/viper.(*Viper).WatchConfig in goroutine 213045
C:/Users/srackHall/go/pkg/mod/github.com/spf13/viper@v1.19.0/viper.go:442 +0x87
exit status 2
Steps To Reproduce
No response
Additional Information
No response
The text was updated successfully, but these errors were encountered: