Skip to content
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

Updating from 2.4.6-p1 to 2.4.6-p4 error #38466

Closed
1 of 5 tasks
dronerdk opened this issue Feb 22, 2024 · 1 comment
Closed
1 of 5 tasks

Updating from 2.4.6-p1 to 2.4.6-p4 error #38466

dronerdk opened this issue Feb 22, 2024 · 1 comment

Comments

@dronerdk
Copy link

Preconditions and environment

Updating from 2.4.6-p1 to 2.4.6-p4 error
PHP 8.1

This error will be present in the terminal when trying to compile magneto:

Repositories code generation... 1/9 [===>------------------------] 11% < 1 sec 203.0 MiB
There is an error in /home/droner_dk_1/public_html/vendor/magento/module-directory-graph-ql/Model/Cache/Tag/Strategy/Config/CurrencyTagGenerator.php at line: 19
Interface "Magento\Store\Model\Config\Cache\Tag\Strategy\TagGeneratorInterface" not found#0 /home/droner_dk_1/public_html/vendor/composer/ClassLoader.php(571): include()
#1 /home/droner_dk_1/public_html/vendor/composer/ClassLoader.php(428): Composer\Autoload\includeFile()
#2 [internal function]: Composer\Autoload\ClassLoader->loadClass()
#3 /home/droner_dk_1/public_html/setup/src/Magento/Setup/Module/Di/Code/Reader/ClassesScanner.php(134): class_exists()
#4 /home/droner_dk_1/public_html/setup/src/Magento/Setup/Module/Di/Code/Reader/ClassesScanner.php(117): Magento\Setup\Module\Di\Code\Reader\ClassesScanner->includeClass()
#5 /home/droner_dk_1/public_html/setup/src/Magento/Setup/Module/Di/Code/Reader/ClassesScanner.php(87): Magento\Setup\Module\Di\Code\Reader\ClassesScanner->extract()
#6 /home/droner_dk_1/public_html/setup/src/Magento/Setup/Module/Di/App/Task/Operation/RepositoryGenerator.php(61): Magento\Setup\Module\Di\Code\Reader\ClassesScanner->getList()
#7 /home/droner_dk_1/public_html/setup/src/Magento/Setup/Module/Di/App/Task/Manager.php(56): Magento\Setup\Module\Di\App\Task\Operation\RepositoryGenerator->doOperation()
#8 /home/droner_dk_1/public_html/setup/src/Magento/Setup/Console/Command/DiCompileCommand.php(216): Magento\Setup\Module\Di\App\Task\Manager->process()
#9 /home/droner_dk_1/public_html/vendor/symfony/console/Command/Command.php(298): Magento\Setup\Console\Command\DiCompileCommand->execute()
#10 /home/droner_dk_1/public_html/vendor/symfony/console/Application.php(1040): Symfony\Component\Console\Command\Command->run()
#11 /home/droner_dk_1/public_html/vendor/symfony/console/Application.php(301): Symfony\Component\Console\Application->doRunCommand()
#12 /home/droner_dk_1/public_html/vendor/magento/framework/Console/Cli.php(116): Symfony\Component\Console\Application->doRun()
#13 /home/droner_dk_1/public_html/vendor/symfony/console/Application.php(171): Magento\Framework\Console\Cli->doRun()
#14 /home/droner_dk_1/public_html/bin/magento(23): Symfony\Component\Console\Application->run()
#15 {main}

Steps to reproduce

update 2.4.6-p1 to 2.4.6-p4 and do a compile

Expected result

...

Actual result

...

Additional information

No response

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”.
Copy link

m2-assistant bot commented Feb 22, 2024

Hi @dronerdk. 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:


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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant