Panic while a program is runing as windows system service

[chenjie4255]

panic: nil passed instead of *os.File to NewColorable()

goroutine 1 [running]:
github.com/mattn/go-colorable.NewColorable(0x0)
	C:/Users/chen/go/pkg/mod/github.com/mattn/go-colorable@v0.1.13/colorable_windows.go:104 +0x3d6
github.com/mattn/go-colorable.NewColorableStdout()
	C:/Users/chen/go/pkg/mod/github.com/mattn/go-colorable@v0.1.13/colorable_windows.go:122 +0x25
github.com/fatih/color.init()
	C:/Users/chen/go/pkg/mod/github.com/fatih/color@v1.13.0/color.go:27 +0x12d

It looks like the os.Stdout may be nil in this case.

It would be better if we could have a method to get around this panic.

[mattn]

NewColorable does not accept nil. On Windows NT Service, os.Stdout always be nil. Can you avoid to use fatih/color in your code?

[mattn]

Or, you can avoid this with below

color.Output = io.Discard
color.Error = io.Discard

[chenjie4255]

NewColorable does not accept nil. On Windows NT Service, os.Stdout always be nil. Can you avoid to use fatih/color in your code?

make sense, I will try to reach out to the faith/color project to see what could be done on their side.

Or, you can avoid this with below

color.Output = io.Discard
color.Error = io.Discard

Thanks for your tips. but where should I put those codes on? since it happened on the go init procedure.

[mattn]

It should be at init func.

func init() {
    if os.Stdout == nil {
        color.Output = io.Discard
        color.Error = io.Discard
    }
}