Default shown in usage is incorrect when the option is supplied

[ericmillin]

my urfave/cli version is

2.1.1

Checklist

• Are you running the latest v2 release? The list of releases is here.
• Did you check the manual for your release? The v2 manual is here
• Did you perform a search about this problem? Here's the Github guide about searching.

Dependency Management

• My project is using go modules.
• My project is using vendoring.
• My project is automatically downloading the latest version.
• I am unsure of what my dependency management setup is.

Describe the bug

If a command fails due to invalid usage, values assigned to valid options are used to populate the defaults.

To reproduce

1. Create the command foo
2. Add the flag fizz and mark it as required.
3. Add the IntFlag bang with the default value of 1.
4. Run the command foo --bang 2

Observed behavior

The default in the usage text will show (default: 2)

Expected behavior

The default in the usage text will show (default: 1)

[asahasrabuddhe]

Unable to reproduce issue. This was the example I tried.

[stale]

This issue or PR has been automatically marked as stale because it has not had recent activity. Please add a comment bumping this if you're still interested in it's resolution! Thanks for your help, please let us know if you need anything else.

[coilysiren]

This looks like a duplicate of #1206, but I would have to dive into the code to say that with confidence.

[stale]

This issue or PR has been bumped and is no longer marked as stale! Feel free to bump it again in the future, if it's still relevant.

[stale]

This issue or PR has been automatically marked as stale because it has not had recent activity. Please add a comment bumping this if you're still interested in it's resolution! Thanks for your help, please let us know if you need anything else.

[stale]

Closing this as it has become stale.

[dearchap]

Unable to reproduce.