Updating symfony/console causing setup:di:compile failure

[Skyfly2021]

Preconditions (*)

1.2.4.2-p1
2.Centos 8
3.php 7.4

Steps to reproduce (*)

Expected result (*)

1. [Screenshots, logs or description]

Actual result (*)

1. [Screenshots, logs or description]
   2.Incompatible argument type: Required type: int. Actual type: string
   The name of the upgrade package is not remembered
   The following error occurred during compilation
   

Workaround

The symfony/console released version 4.4.29 as a hotfix for Magento issue.
For now, you can run composer update symfony/console

Note: the root cause of this issue still not resolved yet

---

Please provide Severity assessment for the Issue as Reporter. This information will help during Confirmation and Issue triage processes.

• 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]

Hi @Skyfly2021. Thank you for your report.
To help us process this issue please make sure that you provided the following information:

• Summary of the issue
• Information on your environment
• Steps to reproduce
• Expected and actual results

Please make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, please, add a comment to the issue:

@magento give me 2.4-develop instance - upcoming 2.4.x release

For more details, please, review the Magento Contributor Assistant documentation.

Please, add a comment to assign the issue: @magento I am working on this

---

• 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, please join the Community Contributions Triage session to discuss the appropriate ticket.

🎥 You can find the recording of the previous Community Contributions Triage on the Magento Youtube Channel

✏️ Feel free to post questions/proposals/feedback related to the Community Contributions Triage process to the corresponding Slack Channel

[cha80]

i am also face this problem 2.3.5-p2

[cha80]

it
might update some module case this problem

[Skyfly2021]

Please downgrade the package, finally solved：
1.composer require symfony/process:4.4.26
2.composer require symfony/console:4.4.26

[brosenberger]

i created a pull request for symfony/console: symfony/symfony#42281 and also any 2.3.x magento2 version is affected.

the problem are the missing php-doc parameters which are checked by the magento2 compiler

[cengizcoskun]

+1

[hostep]

Thanks @brosenberger & @Skyfly2021!

@Skyfly2021: I don't have issues with symfony/process, only with symfony/console

It would be great if Magento's setup:di:compile process could look at the actual argument types and only falls back to the ones in phpdoc when the argument doesn't have a type specified.

Issue will happen for Magento 2.3.5 and higher versions (Magento 2.3.4 restricted symfony/console to max version 4.1.9999)

[kassner]

If you want to patch the issue instead of pinning symfony/console's version:

--- vendor/symfony/console/Input/InputOption.php
+++ vendor/symfony/console/Input/InputOption.php
@@ -48,6 +48,7 @@
     private $description;
 
     /**
+     * @param string $name
      * @param string|array|null                $shortcut The shortcuts, can be null, a string of shortcuts delimited by | or an array of shortcuts
      * @param int|null                         $mode     The option mode: One of the VALUE_* constants
      * @param string|bool|int|float|array|null $default  The default value (must be null for self::VALUE_NONE)

[mortenbirkelund]

Ran into this aswell. Luckily it is a minor patch to add, but hopefully it will be corrected in Symfony.