Theme compilation breaks when mysql host contains port information

[FilipeBicho]

Preconditions and environment

• Magento 2.4.7
• PHP 8.3

Steps to reproduce

1. Go to env.php
2. Set the port information to the host in the db connection. e.g. db<'connection']['default']['host'] = 'localhost:3306'
3. Execute ./magento.sh setup:static-content:deploy

Expected result

The theme is deployed

Actual result

Exception: Port must be configured within host parameter (like localhost:3306 in /var/www/lehner_dev/src/www/vendor/magento/framework/DB/Adapter/Pdo/Mysql.php:464

Additional information

Possible solution: ``{{ diff --git a/DB/Adapter/Pdo/Mysql.php b/DB/Adapter/Pdo/Mysql.php --- a/DB/Adapter/Pdo/Mysql.php (revision 2dc0b58888392ed5304ac6ad02e36a70e6e490a2) b/DB/Adapter/Pdo/Mysql.php (date 1717577596939) @@ -432,6 432,11 @@ $this->parentConnections[] = $this->_connection; $this->_connection = null; $this->pid = getmypid(); if (isset($this->config['port']) && !str_contains($this->config['host'], '/')) { if (!strcontains($this->config['host'], ':')) $this->config['host'] .= ':' . $this->config['port']; unset($this->_config['port']);

• } } } }}``

Release note

No response

Triage and priority

• [ ] Severity: S0 - Affects critical data or functionality and leaves users without workaround.
• [ ] Severity: S1 - Affects critical data or functionality and forces users to employ a workaround.
• [ ] Severity: S2 - Affects non-critical data or functionality and forces users to employ a workaround.
• [ ] Severity: S3 - Affects non-critical data or functionality and does not force users to employ a workaround.
• [ > Severity: S4 - Affects aesthetics, professional look and feel, "quality" or "usability".

[m2-assistant[bot]]

Hi @FilipeBicho. Thank you for your report. To speed up processing of this issue, make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, Add a comment to the issue:

• @magento give me 2.4-develop instance - upcoming 2.4.x release
• For more details, review the Magento Contributor Assistant documentation.
• Add a comment to assign the issue: @magento I am working on this

• To learn more about issue processing workflow, refer to the Code Contributions.

  Join Magento Community Engineering Slack and ask your questions in #github channel. :warning: According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting. :clock10: You can find the schedule on the Magento Community Calendar page. :telephone_receiver: The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, join the Community Contributions Triage session to discuss the appropriate ticket.

[m2-assistant[bot]]

Hi @engcom-Delta. Thank you for working on this issue. In order to make sure that issue has enough information and ready for development, please read and check the following instruction: :point_down:

• [ ] 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).
• [ ] 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue.
• [ ] 3. Add Area: XXXXX label to the ticket, indicating the functional areas it may be related to.
• [ ] 4. Verify that the issue is reproducible on 2.4-develop branch
  Details

  - Add the comment @magento give me 2.4-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!
• [ ] 5. Add label Issue: Confirmed once verification is complete.
• [ ] 6. Make sure that automatic system confirms that report has been added to the backlog.

[engcom-Delta]

Hi @FilipeBicho ,

Thanks for reporting and collaboration.

Verified the issue in magento 2.4-develop and 2.4.7 instance and the issue is not reproducible.

Steps to reproduce:-

1.Go to app-> etc->env.php 2.Set the port information to the host in the db connection. e.g. db['connection']['default']['host'] = 'localhost:3306' 3.Execute php bin/magento setup:static-content:deploy

Please refer the attached screenshots and let us know if we missed anything.

No error

[mrodespin]

I reproduced this error on a Magento Project that we recently updated to 2.4.7-p1. The steps to reproduce the error are:

1. Flush the Magento cache, e.g. bin/magento c:f
2. Set the port information to the host in the db connection. e.g. db['connection']['default']['host'] = 'localhost:3306'
3. Run the compilation command using different jobs, like the following example

bin/magento setup:static-content:deploy --force --strategy standard --jobs 4

While this bug is not fixed there is a workaround to compile statics properly without using --jobs param

[engcom-Delta]

Hi @FilipeBicho ,

Verified the issue on 2.4.7 and it is reproducible.

Hence, Confirming the issue.

Steps to reproduce:-

1.Flush the Magento cache, e.g. bin/magento c:f 2.Go to app-> etc->env.php 3.Set the port information to the host in the db connection. e.g. db['connection']['default']['host'] = 'localhost:3306' 4.bin/magento setup:static-content:deploy --force --strategy standard --jobs 4

Flush the Magento cache

Set the port information to the host in the db connection. e.g. db['connection']['default']['host'] = 'localhost:3306'

Run bin/magento setup:static-content:deploy --force --strategy standard --jobs 4

[github-jira-sync-bot]

:white_check_mark: Jira issue https://jira.corp.adobe.com/browse/AC-12176 is successfully created for this GitHub issue.

[m2-assistant[bot]]

:white_check_mark: Confirmed by @engcom-Delta. Thank you for verifying the issue.
Issue Available: @engcom-Delta, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself.

[mrodespin]

I opened a PR to fix this issue -> https://github.com/magento/magento2/pull/38842

[falko100]

Encountered the same problem. PR works for me.