MySQL Bugs: #100487: Change in behavior for sigint in mysql client in 8.0.20 vs prior versions

Bug #100487	Change in behavior for sigint in mysql client in 8.0.20 vs prior versions
Submitted:	10 Aug 2020 21:13	Modified:	12 Aug 2020 5:15
Reporter:	Carlos Tutte	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Server: Command-line Clients	Severity:	S3 (Non-critical)
Version:	8.0.20	OS:	Any
Assigned to:		CPU Architecture:	Any

Description:
Executing ctrl+C (sigint) at the end of a statement (without a line break) has a different behavior on 8.0.20 vs prior versions.

On 8.0.20:
```
mysql> cancelme ```

sigint will not show anything, until a line break is executed, then  "^C" and a line break is printed

```
mysql> cancelme

^C```

On 8.0.19:
```
mysql> cancelme^C
mysql> 
```

sigint will generate the "^C" char + a line break to be printed

How to repeat:
Write anything on mysql prompt, then hit ctr+C. 
Repeat test in both 8.0.19 and 8.0.20 and check the difference.

Suggested fix:
Behavior should be consistent.

This may be a minor issue functionally, but it's incredibly annoying to users.  Hope this was just some mistake in the build published which will be fixed.

Hello Carlos Tutte,

Thank you for the report and feedback.
Confirmed the reported issue in 8.0.20 but I'm not seeing any issues in 8.0.21(OL7). Could you please check with 8.0.21 build? Thank you.

Thanks,
Umesh

Hi Umesh,

Thanks for checking.

On MySQL 8.0.21 it works as in 8.0.19 and prior version.
Seems the issue is only on 8.0.20

Thank you Carlos Tutte, for confirming that issue no longer exists in latest release. Since this issue has already been fixed in the latest released version hence closing this for now. 

regards,
Umesh