-
Notifications
You must be signed in to change notification settings - Fork 9.3k
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
Database port missing in Magento\TestFramework\Db\Mysql #3529
Comments
Just a little reminder that we need to file a request for this with Magento support. |
gordonknoppe
added a commit
to gordonknoppe/magento2
that referenced
this issue
Apr 22, 2016
- Add port number parsing to connection parameters
Hello @tkn98, this issue has been fixed in the 2.1.0 Release, that's why I'm closing it. If you any questions or additional information regarding the issue feel free to reopen it or create a new one. |
@KrystynaKabannyk: May I ask to share the hash of the commit in which the fix has been applied? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The methods:
Magento\TestFramework\Db\Mysql::storeDbDump()
Magento\TestFramework\Db\Mysql::restoreFromDbDump()
(and perhaps others) are creating mysql / mysqldump commands to be invoked via shell. They make use of the
--host
command-line switch without adressing a potential (optional) port configuration (--port=#
).The configuration format is:
As the configuration data is taken over unchanged, every configuration with a port given makes these CLI commands fail then.
This flaw blocks users with mysql port configuration making use of the test-suite.
Reference: #2735
#2736The text was updated successfully, but these errors were encountered: