Bug #82324 | Fix unclosed socket on constructor (connection) failure (contribution) | ||
---|---|---|---|
Submitted: | 22 Jul 2016 14:43 | Modified: | 12 Jul 2017 15:40 |
Reporter: | OCA Admin (OCA) | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | Connector / Python | Severity: | S3 (Non-critical) |
Version: | OS: | Any | |
Assigned to: | CPU Architecture: | Any | |
Tags: | Contribution |
[22 Jul 2016 14:43]
OCA Admin
[22 Jul 2016 14:43]
OCA Admin
Contribution submitted via Github - Fix unclosed socket on constructor (connection) failure (*) Contribution by Vilnis Termanis (Github vtermanis, mysql-connector-python/pull/22#issuecomment-234535457): I confirm the code being submitted is offered under the terms of the OCA, and that I am authorized to contribute it.
Contribution: git_patch_78457913.txt (text/plain), 1.58 KiB.
[23 Jul 2016 7:03]
MySQL Verification Team
Hello Vilnis Termanis, Thank you for the report and contribution. Thanks, Umesh
[12 Jul 2017 15:40]
Paul DuBois
Posted by developer: Fixed in 2.1.7. Creating a Connection instance with use_pure=True could lead to the underlying socket not being closed if the user name or password were invalid. Thanks to Vilnis Termanis for the patch.