Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Backport] Fix bug with retry connect and custom db port #14753

Merged
merged 2 commits into from Apr 22, 2018
Merged

[Backport] Fix bug with retry connect and custom db port #14753

merged 2 commits into from Apr 22, 2018

Conversation

@julienanquetil
Copy link
Contributor

@julienanquetil julienanquetil commented Apr 18, 2018

Original Pull Request
#14435
Fix a bug in the MySQL adapter when using non standard port

Manual testing scenarios
Use a database config with port, e.g. localhost:3307
On first call to _connect(), the config['host'] parameter is split into config['host'] and config['port']
In the _query() function, a situation happens that is suitable for a retry (e.g. a "MySQL has gone away" error)
_connect() is called again
Expected result
Connection is reestablished and query tried again

Actual result
"Port must be configured within host parameter" exception

Description

Fixed Issues (if relevant)

  1. magento/magento2#<issue_number>: Issue title
  2. ...

Manual testing scenarios

  1. ...
  2. ...

Contribution checklist

  • Pull request has a meaningful description of its purpose
  • All commits are accompanied by meaningful commit messages
  • All new or changed code is covered with unit/integration tests (if applicable)
  • All automated tests passed successfully (all builds on Travis CI are green)
Original Pull Request
#14435
Fix a bug in the MySQL adapter when using non standard port

Manual testing scenarios
Use a database config with port, e.g. localhost:3307
On first call to _connect(), the config['host'] parameter is split into config['host'] and config['port']
In the _query() function, a situation happens that is suitable for a retry (e.g. a "MySQL has gone away" error)
_connect() is called again
Expected result
Connection is reestablished and query tried again

Actual result
"Port must be configured within host parameter" exception
@magento-engcom-team
Copy link
Contributor

@magento-engcom-team magento-engcom-team commented Apr 22, 2018

Hi @julienanquetil. Thank you for your contribution.
Changes from your Pull Request will be available with the upcoming 2.2.5 release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked issues

Successfully merging this pull request may close these issues.

None yet

3 participants