UPSTREAM FIX

magento2-38842: Static content deploy failing when the database host includes a port

Community fix magento2-38842 merged into magento/magento2 on 2024-09-05, released in 2.4.8; applies cleanly to 11 releases from 2.4.7 to 2.4.7-p10.

Fixes static content deploy failing when the database host includes a port edited

Pull request title
Theme compilation breaks when mysql host contains port information
Pull request
magento/magento2#38842
Issues
#38799 human
Author
@mrodespin
Merged
2024-09-05
Fixed in
2.4.8
Reported on
2.4.7
Categories
—
Components
magento/framework

Labels

Area
Performance
Component
DB
Priority
P3
Severity
—
Reported on (labels)
2.4.7

Issue

Title and steps come from the upstream issue and pull request.

Description

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

Steps to reproduce

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

Taken from the upstream issue.

Error signatures

Code match per tag

Each tag was checked with git apply --check against that tag's files. A clean match means the change applies; it is not a test result. Tags that already contain the fix are marked.

LineCode match per tagTests
2.4.6
2.4.6 conflict 2.4.6-p1 conflict 2.4.6-p2 conflict 2.4.6-p3 conflict 2.4.6-p4 conflict 2.4.6-p5 conflict 2.4.6-p6 conflict 2.4.6-p7 conflict 2.4.6-p8 conflict 2.4.6-p9 conflict 2.4.6-p10 conflict 2.4.6-p11 conflict 2.4.6-p12 conflict 2.4.6-p13 conflict 2.4.6-p14 conflict 2.4.6-p15 conflict
2.4.6: no test data 2.4.6-p1: no test data 2.4.6-p2: no test data 2.4.6-p3: no test data 2.4.6-p4: no test data 2.4.6-p5: no test data 2.4.6-p6: no test data 2.4.6-p7: no test data 2.4.6-p8: no test data 2.4.6-p9: no test data 2.4.6-p10: no test data 2.4.6-p11: no test data 2.4.6-p12: no test data 2.4.6-p13: no test data 2.4.6-p14: no test data 2.4.6-p15: no test data
2.4.7
2.4.7 clean 2.4.7-p1 clean 2.4.7-p2 clean 2.4.7-p3 clean 2.4.7-p4 clean 2.4.7-p5 clean 2.4.7-p6 clean 2.4.7-p7 clean 2.4.7-p8 clean 2.4.7-p9 clean 2.4.7-p10 clean
2.4.7: no test data 2.4.7-p1: no test data 2.4.7-p2: no test data 2.4.7-p3: no test data 2.4.7-p4: no test data 2.4.7-p5: no test data 2.4.7-p6: no test data 2.4.7-p7: no test data 2.4.7-p8: no test data 2.4.7-p9: no test data 2.4.7-p10: no test data
2.4.8
2.4.8 conflictcontains the fix 2.4.8-p1 conflictcontains the fix 2.4.8-p2 conflictcontains the fix 2.4.8-p3 conflictcontains the fix 2.4.8-p4 conflictcontains the fix 2.4.8-p5 conflictcontains the fix
2.4.8: no test data 2.4.8-p1: no test data 2.4.8-p2: no test data 2.4.8-p3: no test data 2.4.8-p4: no test data 2.4.8-p5: no test data
2.4.9
2.4.9 conflictcontains the fix
2.4.9: no test data

Triage

Model @cf/cloudflare/clef. Probability this is a bug fix: 97.6%. Probability it is security relevant: 0.7%.

Show the model's answers and probabilities
QuestionAnswerProbabilitiesConfidence
Change kindbugfixbugfix 96.1%, refactor 1.2%, feature 1.0%, dependency 0.6%, tests_only 0.6%, docs_only 0.5%90.8%
Areaframeworkframework 83.2%, frontend 6.6%, other 3.9%65.6%
Reported version2.4.72.4.7 53.4%, 2.4.7-p1 3.0%, 2.4.7-p2 1.5%28.1%
Scope0.43 of 20 65.7%, 1 26.0%, 2 8.3%25.9%
Risk0.59 of 20 59.4%, 1 22.0%, 2 18.5%15.4%
Worth backporting1.52 of 22 61.5%, 1 29.2%, 0 9.3%20.8%

Download

For cweagans/composer-patches, choose a version below and download the bundle. Copy its magento2-38842/ folder into patches/composer/, merge composer.patches.json into composer.json, then run composer install. Test files are always removed; paths are relative to each package root, using the default -p1 level.

Packages (1): magento/framework
Bundle README (what the ZIP ships)
# magento2-38842

Community fix merged upstream into magento/magento2, adapted by magento.watch.
This is not a patch published by Adobe.

Pull request: https://github.com/magento/magento2/pull/38842
Issue: https://github.com/magento/magento2/issues/38799
Author: @mrodespin
Source commit: f050273c65f38e10f72987bb67b48e67ae5883ba
Modifications: test files and documentation removed, paths rewritten relative to each Composer package.
Licence: OSL-3.0 / AFL-3.0, as the original Magento Open Source code.
Maintainer: Łukasz Bajsarowicz (@lbajsarowicz)

Licence: Magento Open Source code under OSL-3.0 and AFL-3.0. The bundle carries the original author, source commit and the list of modifications.

Sources

Łukasz Bajsarowicz
Built by

Łukasz Bajsarowicz, e-commerce architect

Magento and Adobe Commerce architecture, upgrades, performance and audits for merchants and agencies since 2015; magento.watch is the tooling I use on those projects.

Open source, maintained on weekends.