Theme compilation breaks when mysql host contains port information #38799

FilipeBicho · 2024-06-05T09:26:43Z

Preconditions and environment

Magento 2.4.7
PHP 8.3

Steps to reproduce

Go to env.php
Set the port information to the host in the db connection. e.g. db<'connection']['default']['host'] = 'localhost:3306'
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".

The text was updated successfully, but these errors were encountered:

m2-assistant · 2024-06-05T09:26:47Z

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.
⚠️ According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.
🕙 You can find the schedule on the Magento Community Calendar page.
📞 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 · 2024-06-05T09:51:20Z

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: 👇

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 · 2024-06-06T20:13:58Z

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 · 2024-06-17T07:00:31Z

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

Flush the Magento cache, e.g. bin/magento c:f
Set the port information to the host in the db connection. e.g. db['connection']['default']['host'] = 'localhost:3306'
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 · 2024-06-18T14:39:03Z

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 · 2024-06-18T15:02:32Z

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

m2-assistant · 2024-06-18T15:02:35Z

✅ 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 · 2024-06-19T08:21:53Z

I opened a PR to fix this issue -> #38842

falko100 · 2024-08-01T14:21:23Z

Encountered the same problem. PR works for me.

m2-community-project bot added the Issue: ready for confirmation label Jun 5, 2024

engcom-Delta added the Reported on 2.4.7 Indicates original Magento version for the Issue report. label Jun 5, 2024

engcom-Delta self-assigned this Jun 5, 2024

engcom-Delta added the Issue: needs update Additional information is require, waiting for response label Jun 6, 2024

m2-community-project bot removed the Issue: ready for confirmation label Jun 6, 2024

engcom-Delta added Component: DB Reproduced on 2.4.x The issue has been reproduced on latest 2.4-develop branch Area: Performance Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed labels Jun 18, 2024

m2-community-project bot removed the Issue: needs update Additional information is require, waiting for response label Jun 18, 2024

m2-assistant bot unassigned engcom-Delta Jun 18, 2024

mrodespin mentioned this issue Jun 19, 2024

Fix issue when compiling statics with multiple jobs #38842

Merged

m2-community-project bot assigned mrodespin Jun 19, 2024

m2-community-project bot added the Priority: P3 May be fixed according to the position in the backlog. label Jun 20, 2024

engcom-Hotel unassigned mrodespin Jun 21, 2024

m2-community-project bot added the Progress: PR in progress label Jun 21, 2024

engcom-Hotel added this to Low Priority Backlog Aug 19, 2024

engcom-Hotel moved this to Pull Request In Progress in Low Priority Backlog Aug 19, 2024

m2-community-project bot assigned mrodespin Aug 20, 2024

magento-devops-reposync-svc closed this as completed in #38842 Sep 5, 2024

m2-community-project bot removed the Progress: PR in progress label Sep 5, 2024

m2-community-project bot added the Progress: done label Sep 5, 2024

cmuench mentioned this issue Dec 5, 2024

dev:console command issue with 2.4.7 Adobe Commerce Cloud netz98/n98-magerun2#1548

Closed

magento-ct-gh-projects-svc removed this from Low Priority Backlog Jan 22, 2025

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Theme compilation breaks when mysql host contains port information #38799

Theme compilation breaks when mysql host contains port information #38799

FilipeBicho commented Jun 5, 2024 •

edited by github-jira-sync-bot

Loading

m2-assistant bot commented Jun 5, 2024

m2-assistant bot commented Jun 5, 2024

engcom-Delta commented Jun 6, 2024

mrodespin commented Jun 17, 2024 •

edited

Loading

engcom-Delta commented Jun 18, 2024

github-jira-sync-bot commented Jun 18, 2024

m2-assistant bot commented Jun 18, 2024

mrodespin commented Jun 19, 2024

falko100 commented Aug 1, 2024

Theme compilation breaks when mysql host contains port information #38799

Theme compilation breaks when mysql host contains port information #38799

Comments

FilipeBicho commented Jun 5, 2024 • edited by github-jira-sync-bot Loading

Preconditions and environment

Steps to reproduce

Expected result

Actual result

Additional information

Release note

Triage and priority

m2-assistant bot commented Jun 5, 2024

m2-assistant bot commented Jun 5, 2024

engcom-Delta commented Jun 6, 2024

mrodespin commented Jun 17, 2024 • edited Loading

engcom-Delta commented Jun 18, 2024

github-jira-sync-bot commented Jun 18, 2024

m2-assistant bot commented Jun 18, 2024

mrodespin commented Jun 19, 2024

falko100 commented Aug 1, 2024

FilipeBicho commented Jun 5, 2024 •

edited by github-jira-sync-bot

Loading

mrodespin commented Jun 17, 2024 •

edited

Loading