Error message is shown twice.

[lukasmalkmus]

OS: Windows 10 Pro 64bit

If there is a spelling mistake in the command, the error message is printed twice:

Error: unknown command "verson" for "test"

Did you mean this?
        version

Run 'uberctl --help' for usage.
unknown command "verson" for "uberctl"

Did you mean this?
        version

How to reproduce

cobra init test
cd test
cobra add version
go build
./test versin

[dkumor]

Same happens with unknown flags for me.

[at15]

@dkumor @lukasma I found the problem. If you follow the example in readme or use cobra generator, you would have following code in your root command

// Execute adds all child commands to the root command sets flags appropriately.
// This is called by main.main(). It only needs to happen once to the rootCmd.
func Execute() {
    if err := RootCmd.Execute(); err != nil {
        fmt.Println(err)
        os.Exit(-1)
    }
}

comment out the fmt.Println(err) and you won't see the second error message. Because cobra already print the error message in https://github.com/spf13/cobra/blob/master/command.go#L678

if err != nil {
        // If found parse to a subcommand and then failed, talk about the subcommand
        if cmd != nil {
            c = cmd
        }
        if !c.SilenceErrors {
            c.Println("Error:", err.Error())
            c.Printf("Run '%v --help' for usage.\n", c.CommandPath())
        }
        return c, err
    }

But I don't know if this is a special case, if cobra print all the error messages automatically, then we can remove the fmt.Println(err) without worry. (And it should be removed from readme and generator as well to avoid confusion). Otherwise a dirty hack would be check if Did you mean this is in error message, if yes, then we don't print the error since cobra already did.

btw: I am also using Windows 10, but I think this issue is platform independent.

[lukasmalkmus]

Wow, thanks detective 👍
Will definitely use this trick and check if it has some side effects.

[n10v]

@at15 showed right solution. Closing it.

[Ahmed4812]

So I am facing a similar issue. Question is, if there is some unknown issue from the root cmd then how would I handle it if the main/execute doesn't have the print?
@at15